-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
docs(otlp): Restructure OTLP page to elevate propagateTraceparent #16264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
docs/concepts/otlp/otlp-traces.mdx
Outdated
|
|
||
| If you're using OTel without a Sentry SDK, you can send traces directly to Sentry's OTLP endpoint. You can find your endpoint URL and auth key in [Project settings > Client Keys (DSN)](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/). | ||
|
|
||
| ## Known Limitations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nit, but I think it’d be better to move “Known Limitations” to the bottom of the page and bring “Configuration” above the fold, since that’s what most users are looking for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. Updated in 37decf0
coolguyzone
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment, but overall looks good to me! Thanks for cleaning this up 🏄♂️
…6264) Restructures the OTLP concepts section to better highlight the `propagateTraceparent` & OTLP Integration options for users with Sentry + OTel backend setups. **Changes:** **Information Architecture** - Splits the monolithic OTLP index page into focused subpages: - `sentry-with-otel.mdx` - Linking Sentry SDKs with OTel (propagateTraceparent, OTLP Integration) - `otlp-traces.mdx` - Direct OTLP trace ingestion - `otlp-logs.mdx` - Direct OTLP log ingestion - Adds scenario table at the top of index with deep links to relevant sections - Adds distributed trace diagram to visualize Sentry + OTel linking **Content Updates** - Reorders page sections to prioritize common use cases: 1. Linking Sentry and OTLP Traces (propagateTraceparent) 2. OTLP Integration (same service) 3. Sending OpenTelemetry Data (OTel-only backend) - Simplifies language by using "OTel" instead of "OpenTelemetry" in body text - Streamlines setup instructions with clearer deep links to project settings - Adds Node.js (coming soon) placeholder to OTLP Integration section - Clarifies that Sentry does not support OTLP metrics upfront The goal is to make it easier for users to find the right solution for their setup, with Sentry SDK integration options more visible.
Restructures the OTLP concepts section to better highlight the
propagateTraceparent& OTLP Integration options for users with Sentry + OTel backend setups.Changes:
Information Architecture
sentry-with-otel.mdx- Linking Sentry SDKs with OTel (propagateTraceparent, OTLP Integration)otlp-traces.mdx- Direct OTLP trace ingestionotlp-logs.mdx- Direct OTLP log ingestionContent Updates
The goal is to make it easier for users to find the right solution for their setup, with Sentry SDK integration options more visible.