feat(docs): sentry exporter (otel)#16165
Merged
jaffrepaul merged 16 commits intomasterfrom Feb 13, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
d76f458 to
42d556f
Compare
4b14de8 to
cabfea6
Compare
c5ad4ef to
c49634f
Compare
8f3b56a to
5722220
Compare
- Move sentry-exporter.mdx to forwarding/pipelines/ for better organization - Update links in all related pages - Add cross-reference in collector.mdx pointing to Sentry Exporter - Highlight auto-create projects feature in all mentions Co-Authored-By: Claude <noreply@anthropic.com>
sfanahata
reviewed
Feb 13, 2026
| - **[Direct Export](/concepts/otlp/direct/)** - Configure your OTel SDK to send traces and logs directly to Sentry's OTLP endpoints | ||
| - **[Forwarding](/concepts/otlp/forwarding/)** - Use the OpenTelemetry Collector, Vector, or Fluent Bit to forward data from infrastructure sources (CloudWatch, Kafka, Nginx, syslog, etc.) | ||
| - **[Log and Trace Drains](/product/drains/)** - Send telemetry from managed hosting platforms (Vercel, Cloudflare, Heroku, etc.) | ||
| | Method | When to Use | |
Contributor
There was a problem hiding this comment.
Is there a difference in terms of what the experience will be using data through OTel vs Sentry SDK?
Contributor
Author
There was a problem hiding this comment.
Depends on what you mean. Data comes into Sentry via the our SDK or Otel. Once in Sentry users can work with logs, traces and errors (if linked). The experience getting the data in may be different but once it's in, it's Sentry. The only thing I can think of is some nuance with the level of trace connected-ness to errors.
sfanahata
reviewed
Feb 13, 2026
sfanahata
reviewed
Feb 13, 2026
sfanahata
approved these changes
Feb 13, 2026
Contributor
sfanahata
left a comment
There was a problem hiding this comment.
Nothing blocking but left a few comments. Nice one!
…ction Expand the alpha stability alert to set clearer expectations about potential configuration changes. Remove the AI-Assisted Setup section to streamline the documentation. Co-Authored-By: Claude <noreply@anthropic.com>
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
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.
Summary
Adds documentation for the Sentry Exporter in the OpenTelemetry Collector, which routes telemetry from multiple services to different Sentry projects through a single collector instance.
sentryvsotlphttpexporterIS 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:
🤖 Generated with Claude Code