Problem Statement

OpenTelemetry has growing popularity in the observability space as one of the top CNCF open standard for APM.

It's data model differs from Sentry so it cannot be natively ingested. But many OpenTelemetry users would like to send their OTEL data to Sentry.

Solution Brainstorm

Details

• SDK Docs: OpenTelemetry Support | Sentry
• span processor - transforming OTEL spans into Sentry spans within Sentry transactions
  • span name, description and span status
    • span status needs special logic for DiagnosticSource versions < 6.0.0
  • parent child relationships
• trace/context propagator - including DSC and trace context
  • https://opentelemetry.io/docs/reference/specification/context/api-propagators/

dogfooding

The cartservice on our OTel Demo is .NET

https://github.com/getsentry/opentelemetry-demo/tree/main/src/cartservice

Reference

Demo project from OTEL, we created a fork to instrument with Sentry SDKs, to test and demo the implementation. Projects are in the Sentry SDKs org

• https://github.com/getsentry/opentelemetry-demo

For more context, these PRs are not exhaustive list of the work done on other SDKs

• Ruby: Ruby SDK basic OTEL Support sentry-ruby#1907

• Python: Basic OpenTelemetry (OTEL) Support sentry-python#1687

• Node: Add OpenTelemetry Node Package sentry-javascript#6000 & [OTEL] Add instrumenter option to Node SDK & disable auto-instrumentation sentry-javascript#6127

• Java: Java SDK basic OTEL Support sentry-java#2327

  • Add SpanProcessor for OTEL sentry-java#2357
  • Add contexts to SentryTracer and add otel context to it sentry-java#2361

• Relay: Add OpenTelemetry span transformation relay#1636

  • efforts to consolidate the logic so the SDKs do not have to as much