feat(otlp): Add python OTLP integration #15093
Open
+83
−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.
1 Skipped Deployment
|
Bundle ReportChanges will increase total bundle size by 411 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
sl0thentr0py
force-pushed
the
neel/python-poc-otlp
branch
from
a3a3464 to
5f21a72
Compare
sl0thentr0py
force-pushed
the
neel/python-poc-otlp
branch
2 times, most recently
from
279511d to
68ec4fc
Compare
sl0thentr0py
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
sl0thentr0py
force-pushed
the
neel/python-poc-otlp
branch
from
68ec4fc to
ef9e9f7
Compare
sfanahata
reviewed
Nov 6, 2025
|
|
||
| ## Dedicated Integrations | ||
|
|
||
| The following SDKs have dedicated integrations that make setting up OTLP a breeze. |
There was a problem hiding this comment.
Is this POTEL, or is there something else we've recently done to make Python specifically easier to set up?
There was a problem hiding this comment.
the original POTEL project is dead
this is the first of the OTLP SDKs which is the project that replaces POTEL leveraging our new OTLP ingestion support
sfanahata
reviewed
Nov 6, 2025
| keywords: ["otlp", "otel", "opentelemetry"] | ||
| --- | ||
|
|
||
| The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an [OpenTelemetry](https://opentelemetry.io) SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). |
There was a problem hiding this comment.
I love links to all the information, but also having 3 in a row can make it hard to know what I'm focusing on. I suggest dropping the general one, as I assume people who land here will go to the protocol and then can dig in on otel.
Suggested change
| The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an [OpenTelemetry](https://opentelemetry.io) SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). | |
| The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). |
sfanahata
reviewed
Nov 6, 2025
|
|
||
| ### OpenTelemetry | ||
|
|
||
| For the OpenTelemetry SDK, you need to [configure instrumentation](https://opentelemetry.io/docs/languages/python/getting-started/#instrumentation) as per your needs. |
There was a problem hiding this comment.
Suggested change
| For the OpenTelemetry SDK, you need to [configure instrumentation](https://opentelemetry.io/docs/languages/python/getting-started/#instrumentation) as per your needs. | |
| For the OpenTelemetry SDK, you need to [configure instrumentation](https://opentelemetry.io/docs/languages/python/getting-started/#instrumentation) you want to capture. |
sfanahata
reviewed
Nov 6, 2025
|
|
||
| For the Sentry SDK, you simply need to enable our `OTLPIntegration` along with your existing configuration. | ||
|
|
||
| <OnboardingOptionButtons |
There was a problem hiding this comment.
Should this also call out tracing? It sounds like tracing is also auto opt-in like error monitoring, and we should show that.
There was a problem hiding this comment.
people should not use our tracing when they use opentelemetry tracing, it's going to either or. Maybe we should clarify that?
There was a problem hiding this comment.
Yeah, I think it's a simple clarification. I added a suggestion in the behavior section below.
sfanahata
reviewed
Nov 6, 2025
|
|
||
| * A [`SpanExporter`](https://opentelemetry.io/docs/concepts/components/#exporters) that will automatically setup the OTLP ingestion endpoint from your Sentry DSN | ||
| * A [`Propagator`](https://opentelemetry.io/docs/concepts/context-propagation/#propagation) that ensures [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/) works | ||
| * Trace/Span linking for all other Sentry events such as Errors, Logs, Crons and Metrics |
There was a problem hiding this comment.
Does it make sense to call out that Logs, Crons, and Metrics require additional config?
sfanahata
reviewed
Nov 6, 2025
|
|
||
| <Alert> | ||
|
|
||
| We have a dedicated <PlatformLink to="/integrations/otlp"> OTLPIntegration </PlatformLink> now that can directly ingest OpenTelemetry Traces into Sentry. We recommend moving over to the new setup since it is much simpler. |
There was a problem hiding this comment.
Suggested change
| We have a dedicated <PlatformLink to="/integrations/otlp"> OTLPIntegration </PlatformLink> now that can directly ingest OpenTelemetry Traces into Sentry. We recommend moving over to the new setup since it is much simpler. | |
| We now have a dedicated <PlatformLink to="/integrations/otlp"> OTLPIntegration</PlatformLink> that can directly ingest OpenTelemetry Traces into Sentry. We recommend moving over to the new setup since it is much simpler. |
sfanahata
reviewed
Nov 6, 2025
| sidebar_order: 20 | ||
| --- | ||
|
|
||
| <Alert> |
There was a problem hiding this comment.
Suggested change
| <Alert> | |
| <Alert title="New Integration Option"> |
sfanahata
reviewed
Nov 6, 2025
|
|
||
| Under the hood, the `OTLPIntegration` will setup the following parts: | ||
|
|
||
| * A [`SpanExporter`](https://opentelemetry.io/docs/concepts/components/#exporters) that will automatically setup the OTLP ingestion endpoint from your Sentry DSN |
There was a problem hiding this comment.
Suggested change
| * A [`SpanExporter`](https://opentelemetry.io/docs/concepts/components/#exporters) that will automatically setup the OTLP ingestion endpoint from your Sentry DSN | |
| * A [`SpanExporter`](https://opentelemetry.io/docs/concepts/components/#exporters) that will automatically setup the OTLP ingestion endpoint from your Sentry DSN. This enables tracing in Sentry. **Note:** _Do not_ also set up tracing via the Python SDK. |
sfanahata
reviewed
Nov 6, 2025
| @@ -1,2 +1,2 @@ | |||
| --- | |||
| title: OpenTelemetry Support | |||
There was a problem hiding this comment.
Suggested change
| title: Legacy OpenTelemetry Integration Support |
sfanahata
requested changes
Nov 6, 2025
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.
merge after getsentry/sentry-python#4877 is released
Issues