You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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
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
changed the title
Disable tracing for nginx in datadog for specific Path group
Disable NGINX OTEL tracing for specific path(s)
Aug 20, 2024
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.
The text was updated successfully, but these errors were encountered: