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

How to filter based on exception.type #31845

Closed
commonfurture opened this issue Mar 20, 2024 · 4 comments
Closed

How to filter based on exception.type #31845

commonfurture opened this issue Mar 20, 2024 · 4 comments
Labels
closed as inactive question Further information is requested Stale

Comments

@commonfurture
Copy link

Component(s)

No response

Describe the issue you're reporting

How to filter based on exception.type
image
image

@commonfurture commonfurture added the needs triage New item requiring triage label Mar 20, 2024
@JaredTan95
Copy link
Member

JaredTan95 commented Mar 20, 2024

you can filter in findTrace page with tags .
BTW, To better solve your problem, you can move this issue to the jaeger community

@JaredTan95 JaredTan95 added question Further information is requested and removed needs triage New item requiring triage labels Mar 20, 2024
@swar8080
Copy link
Contributor

If that UI doesn't let you filter on span event attributes then you could copy exception.type as a span attribute:

      transform:
        error_mode: ignore
        trace_statements:
          - context: spanevent
            statements:
              - set(span.attributes["exception.type"], attributes["exception.type"])

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label May 20, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed as inactive question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

3 participants