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
POTEL 33 - Record dropped spans when sampling OpenTelemetry spans (#3552)
* Use parent span id from sentry-trace header
* attach active span to scope
* record dropped span/transaction in SentrySampler
* changelog
* record lost span when copying parent decision
* Format code
* refactor: use sampling decision
---------
Co-authored-by: Sentry Github Bot <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@
9
9
- Traces were broken because on an incoming request, OtelSentrySpanProcessor did not set the parentSpanId on the span correctly. Traces were not referencing the actual parent span but some other (random) span ID which the server doesn't know.
10
10
- Attach active span to scope when using OpenTelemetry ([#3549](https://github.com/getsentry/sentry-java/pull/3549))
11
11
- Errors weren't linked to traces correctly due to parts of the SDK not knowing the current span
12
+
- Record dropped spans in client report when sampling out OpenTelemetry spans ([#3552](https://github.com/getsentry/sentry-java/pull/3552))
0 commit comments