Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable NGINX OTEL tracing for specific path(s) #737

Open
slarwise opened this issue Jul 5, 2022 · 2 comments
Open

Disable NGINX OTEL tracing for specific path(s) #737

slarwise opened this issue Jul 5, 2022 · 2 comments

Comments

@slarwise
Copy link
Contributor

slarwise commented Jul 5, 2022

This tracing results in around 200-300 spans per second for posting metrics, which results in a lot of noise. It is useful to have tracing enabled for nginx when the applications are used, since services might communicate with each other through nginx, and then we want the trace information to be propagated over nginx. Ideally we would disable tracing for the metrics endpoint only.

@NissesSenap
Copy link
Contributor

@slarwise can't remember exactly what this is about.
Can you share a print screen or something.

Do I understand you correctly that each time the health endpoint of ingress-nginx is queries datadog generates a traces?

@NissesSenap NissesSenap changed the title Disable tracing for nginx when datadog is used as tracing provider Disable tracing for nginx in datadog for specific Path group Jul 28, 2022
@landerss1 landerss1 changed the title Disable tracing for nginx in datadog for specific Path group Disable NGINX OTEL tracing for specific path(s) Aug 20, 2024
@landerss1
Copy link
Contributor

NGINX DataDog specific tracing is deprecated in favor of OTEL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants