DRAFT: Add CLIENT spans and trace context injection for vMCP backends #3684
+134
−23
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
SpanKindClientspans to the vMCP telemetry backend client with standard MCP OTEL attributesmcp.client.operation.durationhistogram using sharedMCPOperationDurationBucketsfrom telemetry packageserver.portto beintper OTEL conventions (wasstring)error.typeto use error message instead of Go type name (%T)traceparent/tracestate) into outgoing MCP tool call requests viaparams._meta%winfmt.Errorf(changed to%vfor second error)Addresses #3399.
PR Stack (3/3): #3682 (propagation) → #3683 (metrics/attributes) → This PR
Test plan
go build ./...passesgo test ./pkg/vmcp/server/...passesgo test ./pkg/vmcp/client/...passestask lint-fixpasses with 0 issuesresolveServerAddrPortreturns(string, int)andattrServerPort.Int()is used🤖 Generated with Claude Code