feat(otlp): Add develop docs for OTLPIntegration #15548
Open
+101
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
2 times, most recently
from
a2ab569 to
4d873b4
Compare
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
from
4d873b4 to
e36f698
Compare
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
from
e36f698 to
8fef46f
Compare
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
2 times, most recently
from
b289917 to
c861c3c
Compare
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
from
c861c3c to
47e7881
Compare
Bundle ReportChanges will increase total bundle size by 52.59kB (0.22%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
Files in
view changes for bundle: sentry-docs-server-cjsAssets Changed:
Files in
App Routes Affected:
|
sl0thentr0py
force-pushed
the
neel/otlp-develop
branch
from
47e7881 to
0efe4c0
Compare
AbhiPrasad
reviewed
Nov 20, 2025
| It MUST consist of and setup the following components: | ||
|
|
||
| * A `SpanExporter` that automatically configures the OTLP ingestion endpoint from the DSN | ||
| * A `Propagator` that ensures Distributed Tracing works with other upstream and downstream services using Sentry SDKs |
Member
There was a problem hiding this comment.
Can we also specify this works by attaching a sentry-trace header, and NOT a traceparent header here?
|
|
||
| ### SpanExporter | ||
|
|
||
| IF `setup_otlp_exporter` is `True`, the integration MUST do the following: |
Member
There was a problem hiding this comment.
should we make this name traces specific?
Because it might also make sense to have one for logs as well.
| IF `setup_otlp_exporter` is `True`, the integration MUST do the following: | ||
|
|
||
| * Take the existing `TracerProvider` from OpenTelemetry if it exists, otherwise create a new one | ||
| * Construct the OTLP Traces `endpoint` from the DSN |
Member
There was a problem hiding this comment.
Construct the OTLP Traces
endpointfrom the DSN
We should add docs for this.
|
|
||
| * A `SpanProcessor` for processing and packaging the Spans that OpenTelemetry emits | ||
| * A `Propagator` that ensures Distributed Tracing works with other upstream and downstream services using Sentry SDKs | ||
| * A `Sampler` that works with Sentry's `traces_sample_rate` and `traces_sampler` |
Member
There was a problem hiding this comment.
might be worth leaving an extra note about why we don't need a sampler for this setup anymore.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
preview: https://develop-docs-git-neel-otlp-develop.sentry.dev/sdk/telemetry/traces/otlp/
resolves
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: