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
This is because when our SpanProcessor handles the OpenTelemetry span with the exception recorded in it, we don't have access to the original exception and so we have to recreate a "poor man's" exception instead.
Our deduplication then doesn't, since it matches by reference.
The following code will result in duplicate exceptions events being reported to Sentry:
This is because when our SpanProcessor handles the OpenTelemetry span with the exception recorded in it, we don't have access to the original exception and so we have to recreate a "poor man's" exception instead.
Our deduplication then doesn't, since it matches by reference.
We could come up with a work around this but it makes more sense to address the issue in OpenTelemetry. See open-telemetry/opentelemetry-dotnet#2439 (comment) for details.
The text was updated successfully, but these errors were encountered: