- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.7k
Closed
Description
We've published the package https://www.npmjs.com/package/@sentry/opentelemetry-node! Please give it a try and let us know what you think!
Problem Statement
Details
- https://develop.sentry.dev/sdk/performance/opentelemetry/
- span processor - transforming OTEL spans into Sentry spans within Sentry transactions
- span name and description
- parent child relationships
 
- trace/context propagator - including DSC and trace context
Reference
Ruby issues with initial implementation getsentry/sentry-ruby#1907
Solution Brainstorm
Todo:
In Progress:
Done:
-  Add @sentry/opentelemetry-nodepackage feat(otel): Add initial package for otel #6002
-  Add basic span processor to @sentry/opentelemetry-nodefeat(otel): Add basic SentrySpanProcessor #6023
- Add tests for span processor feat(otel): Add basic SentrySpanProcessor #6023
- Add otel context to transaction events feat(otel): Map otel span data to Sentry transaction/span/context #6082
- Add ops, description mapping functionality feat(otel): Parse better op/description from otel span where possible #6084
- [OTEL] Test processor & setup with demo app #6112
-  [OTEL] Add propagator support #6107
- Initial attempt here: feat(otel): Add propagator #6095
 
-  [OTEL] Add instrumenteroption to Node SDK & disable auto-instrumentation #6127
-  Update README for alpha state of @sentry/opentelemetry-nodechore(otel): Update README to add alpha note #6169
-  Publish @sentry/opentelemetry-nodePackage https://www.npmjs.com/package/@sentry/opentelemetry-node
smeubank, mydea, SimenB and Lms24