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
{{ message }}
This repository was archived by the owner on Aug 14, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/docs/sdk/performance/opentelemetry/index.mdx
+42-4Lines changed: 42 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,54 @@ TODO: Add history about OpenTelemetry Sentry Exporter: https://github.com/open-t
22
22
23
23
TODO: Talk about the approach we are using, based on Matt's hackweek project - https://github.com/getsentry/sentry-ruby/pull/1876
24
24
25
-
## OpenTelemetry Context
26
-
27
-
TODO: Do we add OpenTelemetry Event Context?
28
-
29
25
## Transaction Protocol
30
26
31
27
TODO: Talk about generating transactions
32
28
33
29
import"./span-protocol.mdx"
34
30
31
+
## OpenTelemetry Context
32
+
33
+
Aside from information from Spans and Transactions, OpenTelemetry has meta-level information about the SDK, resource, and service that generated spans. To track this information, we generate a new OpenTelemetry Event Context.
34
+
35
+
The existence of this context on an event (transaction or error) is how the Sentry backend will know that the incoming event is an OpenTelemetry event.
0 commit comments