feat: add OpenTelemetry tracing for client and server requests#2025
Open
feat: add OpenTelemetry tracing for client and server requests#2025
Conversation
Add opentelemetry-api as a dependency and instrument BaseSession.send_request() with a CLIENT span per outgoing request. This establishes the tracing foundation for the SDK. Each request gets a span with the MCP method name and, where applicable, the target name (tool name, prompt name, resource URI). Spans record OK/ERROR status and error type attributes. Excluded methods (e.g. notifications/message) are skipped.
Kludex
commented
Feb 10, 2026
tests/shared/test_tracing.py
Outdated
Comment on lines
1
to
4
Member
Author
There was a problem hiding this comment.
It seems it does. I can see the py.typed.
Kludex
commented
Feb 10, 2026
src/mcp/shared/session.py
Outdated
Member
Author
There was a problem hiding this comment.
Is there a case that we don't have a method?
Kludex
commented
Feb 10, 2026
src/mcp/shared/tracing.py
Outdated
Comment on lines
35
to
39
Member
Author
There was a problem hiding this comment.
No need for this utility.
Kludex
commented
Feb 10, 2026
tests/shared/test_tracing.py
Outdated
Comment on lines
134
to
136
Member
Author
There was a problem hiding this comment.
Is it possible to use mcp.client.Client instead?
Kludex
commented
Feb 10, 2026
tests/shared/test_tracing.py
Outdated
Comment on lines
66
to
74
Member
Author
There was a problem hiding this comment.
We shouldn't test private functions! Please document that in the CLAUDE.md.
Kludex
commented
Feb 10, 2026
tests/shared/test_tracing.py
Outdated
Comment on lines
51
to
63
Member
Author
There was a problem hiding this comment.
We shouldn't test private functions! Please document that in the CLAUDE.md.
- Remove pyright suppressions (opentelemetry-sdk ships py.typed)
- Use `request_data["method"]` instead of `.get("method", "")`
- Inline `_build_span_name` into `start_client_span`
- Remove unit tests for private functions, test through E2E instead
- Rewrite error test to use `Client` (timeout-based)
- Add "do not test private functions" rule to CLAUDE.md
Kludex
commented
Feb 10, 2026
src/mcp/shared/session.py
Outdated
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Instrument the server side of MCP request handling with OpenTelemetry SERVER spans. The span starts after request validation in _receive_loop and ends when RequestResponder.respond() or cancel() is called, covering the full server-side request lifecycle.
Kludex
changed the title
Kludex
commented
Feb 10, 2026
src/mcp/shared/session.py
Outdated
Comment on lines
368
to
371
Member
Author
There was a problem hiding this comment.
Single line please. Is the method not always available in request_data?
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
1 participant
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
opentelemetry-apias a runtime dependency andopentelemetry-sdkas a dev dependencysrc/mcp/shared/tracing.pywith a module-level tracer, attribute constants, and helpers for span naming (including target extraction fortools/call,prompts/get,resources/read)BaseSession.send_request()with a singleCLIENTspan per outgoing request — records method name, target, OK/ERROR status, and error typenotifications/message) produce no spanThis is the minimal foundation for OpenTelemetry support. No context propagation, metrics, or server-side spans yet — just one client-side span per request to establish the pattern.
Test plan
_extract_target()and_build_span_name()helpers (parametrized)send_ping()tools/callrequestserror.typeattribute on JSON-RPC error responseruff format+ruff checkpasspyrightstrict passes (0 errors)