-
Notifications
You must be signed in to change notification settings - Fork 391
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
Support filtering traces by request path #1416
Comments
Shouldn't this be a generic filter based on span properties? |
Maybe, but exposing a first-class UI ability to filter by incoming request path built on top of a generic filter would likely be useful. |
I don't think we should do that. These are spans (activities), not requests. |
Yes understood. What is the span-centric way of describing what's being shown? Is it just the display name or is the dashboard special-casing different span types and extracting specific info. for display here? |
Are you asking to filter the requests in the UI, or suppress them being sent based on the type of the request. The latter is possible though the OTEL APIs to create a sampler that can work at the head or tail level. |
Filter in the UI |
Discussed in #1390
Originally posted by Kralizek December 14, 2023
My ASP.NET Core app with Razor Pages emits traces for static content. Is it possible to specify paths that should be ignored?
I also get traces for requests originated by the AWS SSM configuration provider.
Ideally, I'd love the traces to be less noisy:
Some screenshots:
The text was updated successfully, but these errors were encountered: