feat(develop): Add distributed tracing for MCP #15752
Open
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
|
betegon
approved these changes
Dec 9, 2025
Member
betegon
left a comment
betegon
left a comment
There was a problem hiding this comment.
Looks good!
btw we don't support mcp clients, is something we're considering now?
This was referenced Dec 9, 2025
AbhiPrasad
approved these changes
Dec 9, 2025
cleptric
reviewed
Dec 10, 2025
Comment on lines
+177
to
+190
| ## Distributed Tracing | ||
|
|
||
| Traces should be continued when a client makes a tool call request to an MCP server and both the client and server are instrumented. To do so, we inject both the trace parent (sentry-trace) and baggage into the `_meta` field of the request, and pick these up on the server. The tracing metadata attached in the `_meta` field is the same as the metadata contained in HTTP headers in HTTP-based trace continuation. | ||
|
|
||
| The SDK must respect any existing metadata in `_meta`. If previously empty, the `_meta` field must have the form | ||
|
|
||
| ```json | ||
| "_meta": { | ||
| "sentry-trace": "...", | ||
| "baggage": "...", | ||
| } | ||
| ``` | ||
|
|
||
| where "sentry-trace" is analogous to the [`sentry-trace` HTTP header](/sdk/telemetry/traces/#header-sentry-trace) and "baggage" is analogous to [`baggage` HTTP header](/sdk/telemetry/traces/dynamic-sampling-context/#baggage-header). |
Member
There was a problem hiding this comment.
Maybe we can already think about how we can support mixed OTLP/Sentry instrumentation here. As in, can we rely on the traceparent header instead of our sentry-tace header?
Also, which options should define if we perform propagation? tracePropagationTargets or something new?
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
Add specification for trace propagation over the MCP protocol.
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:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES