-
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
Sentry exporter: Add stack trace to error events #35887
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
exporter/sentry
Is your feature request related to a problem? Please describe.
Adding stack traces to sentry exporter errors would make debugging issues easier. Currently there doesn't seem to be any mapping between any field in the trace and the Stack Trace Frames in sentry.
Describe the solution you'd like
A mapping between semconv Exceptions and sentry stack traces.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: