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

API UI failing for error events derived from traces with Jaeger agent #12986

Closed
lahsivjar opened this issue Apr 17, 2024 · 0 comments · Fixed by elastic/apm-data#272
Closed
Assignees
Labels
bug impact:high Short-term priority; add to current release, or definitely next.

Comments

@lahsivjar
Copy link
Contributor

lahsivjar commented Apr 17, 2024

APM Server version (apm-server version): 8.x

Description of the problem including expected versus actual behavior: APM UI requires the existence of error.id for error events. For OpenTelemetry, the support for adding error.id was added via #9178. Unfortunately, Jaeger agents for traces are handled in a special way (ref) which doesn't include the fix.

Steps to reproduce:

  1. Send error traces with Jaeger/* as the agent name.
  2. Observe the indexed document to not have error.id

Provide logs (if relevant): N/A

@lahsivjar lahsivjar added bug impact:high Short-term priority; add to current release, or definitely next. labels Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug impact:high Short-term priority; add to current release, or definitely next.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants