-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Filtering Tracing on v0.109.0 #36409
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hi @baikunthasahoo! Can you check whether something like the following config may help you to achieve this? This makes use of the
With this config, the following span was filtered as expected:
|
Thanks for your quick support. Here i want suppress the /api/healthz noise. Does above example will suppress the ./api/healthz. ? |
Yes, this configuration will filter out all spans with the |
Thank so much !! @bacherfl Its working for me. |
awesome, thanks for the update! |
Component(s)
processor/filter
Describe the issue you're reporting
Hi Team,
I am trying to exclude spans in the OpenTelemetry Collector using the filterprocessor. Specifically, I need to exclude spans where the next.route attribute matches the following values:
/api/healthz
/[locale]/api/healthz (where [locale] is dynamic, e.g., /en, /fr, etc.)
Despite configuring the filterprocessor with a regular expression, I am still seeing these spans in the traces. Below are the steps, configurations, and behaviors observed.
filter/exclude-health-api-traces:
spans:
exclude:
match_type: regexp
attributes:
- key: "http.target"
value: ".\/api\/healthz."
I need your support on above query
Note: I have deployed my application in Kubernetes and used health probes for every 10sc. my application send data to collector as daemonset from otel collector i am exporting my traces.
The text was updated successfully, but these errors were encountered: