You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing the issue on sentry.io, the exception should have a link to the relevant trace. When viewing the trace, the exception should be shown in the trace view.
Thanks for writing in.
I do confirm that the error event sent to Sentry does indeed not contain the required contexts.trace values to make the link between the transaction and error work.
Summary
When creating a transaction and a trace and then doing
sentry.CaptureException(err)
, the error is not linked to the trace properly.Steps To Reproduce
Expected Behavior
When viewing the issue on sentry.io, the exception should have a link to the relevant trace. When viewing the trace, the exception should be shown in the trace view.
Screenshots
Sentry.io Event
Error Event: 120248f44d174a1a8d2a60073153e75a
Trace Event: 7b8eaba5361f4c698e79508fa6af68f4
Environment
SDK
sentry-go
version:v0.15.0
1.19.3
yes
Sentry
yes
The text was updated successfully, but these errors were encountered: