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
Span links were added in #4486, but are currently only accessible as
part of transaction events. We would like to get them in EAP. The first
step in that process is to add them to serialized Kafka spans.
The integration tests confirm production into Kafka for every current
path for links to enter the system:
- in a transaction event's trace context
- in a transaction event's child spans
- in a `span` envelope item
- in an `otel_span` envelope item
- via OTLP JSON
- via OTLP gRPC
Note that our version of the `opentelemetry-proto` Python library is too
old to make `flags` available so not all tests could check the `sampled`
handling. I'll handle that in a future PR.
---------
Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Co-authored-by: Sigrid Huemer <32902192+s1gr1d@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,7 @@
42
42
- Add `/v1/traces` (without a trailing slash) as a spec-compliant alternative for our OTLP traces endpoint. ([#4655](https://github.com/getsentry/relay/pull/4655))
43
43
- Improve handling of failed Redis connections. ([#4657](https://github.com/getsentry/relay/pull/4657))
44
44
- Expose new metrics from the async pool. ([#4658](https://github.com/getsentry/relay/pull/4658))
45
+
- Serialize span's `links` information when producing to Kafka. ([#4601](https://github.com/getsentry/relay/pull/4601))
0 commit comments