feat(otlp): Add basic OTLP beta documentation #14453
Merged
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 Git ↗︎
1 Skipped Deployment
|
Bundle ReportChanges will increase total bundle size by 1.93kB (0.01%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
Files in
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
Files in
|
coolguyzone
reviewed
Jul 28, 2025
AbhiPrasad
reviewed
Jul 28, 2025
Co-authored-by: Alex Krawiec <[email protected]>
Co-authored-by: Abhijeet Prasad <[email protected]>
sergical
reviewed
Jul 28, 2025
There was a problem hiding this comment.
Just my 🪙🪙 also not sure if additional resources need to be updated: https://develop.sentry.dev/sdk/telemetry/traces/opentelemetry/
|
@AbhiPrasad @coolguyzone @sergical updated the PR with all of your suggestions, thanks! Please take a peek, and let me know if any other changes are needed |
AbhiPrasad
approved these changes
Jul 28, 2025
|
@AbhiPrasad 👍🏻 done, better to be explicit |
gggritso
deleted the
georgegritsouk/ope-18-write-public-onboarding-documentation-for-otlp-in-saas
branch
lucas-zimerman
pushed a commit
that referenced
this pull request
Jul 29, 2025
## DESCRIBE YOUR PR Sentry is working on OTLP ingestion! This'll allow customers to configure their OpenTelemetry SDKs to send traces directly to Sentry. This is a major departure from our current OTLP support, which mostly requires users to configure their SDKs in special ways. We are gearing up for a Limited Availability Beta with a few select customers. While we expect to hold their hand for a lot of it, it's still a good idea to have some public documentation they can refer to. I'm looking for feedback from the Docs team on where to best place this kind of generic documentation (I took a shot!) and from the SDKs team for how to make this document play nice with existing SDK documentation about OpenTelemetry. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [x] None: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [x] Checked Vercel preview for correctness, including links - [x] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [x] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Alex Krawiec <[email protected]> Co-authored-by: Abhijeet Prasad <[email protected]>
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.
DESCRIBE YOUR PR
Sentry is working on OTLP ingestion! This'll allow customers to configure their OpenTelemetry SDKs to send traces directly to Sentry. This is a major departure from our current OTLP support, which mostly requires users to configure their SDKs in special ways.
We are gearing up for a Limited Availability Beta with a few select customers. While we expect to hold their hand for a lot of it, it's still a good idea to have some public documentation they can refer to.
I'm looking for feedback from the Docs team on where to best place this kind of generic documentation (I took a shot!) and from the SDKs team for how to make this document play nice with existing SDK documentation about OpenTelemetry.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST