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
Associating errors with transactions is generally implemented (see otel/event_processor.go), but there's a caveat: the EventHint of the event processor has to contain a valid Context with a set OpenTelemetry span. This means that e.g. messages captured with sentry.CaptureMessage or hub.CaptureMessage won't be linked to Sentry spans at the moment.
So to properly link the raised exception now users have to do things like:
We might want to expose methods like CaptureMessageWithContext(ctx context.Context, message string) and others that also take a ctx parameter. Under the hood, they would set add the passed ctx to EventHint.
The text was updated successfully, but these errors were encountered:
Extracted from #537.
Problem
Associating errors with transactions is generally implemented (see
otel/event_processor.go
), but there's a caveat: theEventHint
of the event processor has to contain a valid Context with a set OpenTelemetry span. This means that e.g. messages captured withsentry.CaptureMessage
orhub.CaptureMessage
won't be linked to Sentry spans at the moment.So to properly link the raised exception now users have to do things like:
Proposed Solution
We might want to expose methods like
CaptureMessageWithContext(ctx context.Context, message string)
and others that also take actx
parameter. Under the hood, they would set add the passedctx
toEventHint
.The text was updated successfully, but these errors were encountered: