Skip to content

Conversation

@Rambatino
Copy link
Contributor

  • Extract trace headers (traceparent, tracestate, x-trace-id, x-request-id) from incoming requests
  • Add traceHeaders field to ServerProps type
  • Pass trace headers through to MCP server context
  • Leverage existing @microlabs/otel-cf-workers instrumentation for automatic propagation
  • Maintain compatibility with Axiom trace publishing configuration

@Rambatino Rambatino requested a review from njpatel October 7, 2025 13:53
@njpatel
Copy link
Member

njpatel commented Oct 8, 2025

is this missing the connection to the client in core so it propagates the traceHeaders on requests?

- Extract trace headers (traceparent, tracestate, x-trace-id, x-request-id) from incoming requests
- Add traceHeaders field to ServerProps type
- Pass trace headers through to MCP server context
- Leverage existing @microlabs/otel-cf-workers instrumentation for automatic propagation
- Maintain compatibility with Axiom trace publishing configuration
@Rambatino Rambatino force-pushed the feat/trace-header-propagation branch from d1154c0 to 26be126 Compare October 8, 2025 11:12
@Rambatino
Copy link
Contributor Author

is this missing the connection to the client in core so it propagates the traceHeaders on requests?

yeah getting the full end to end picture of the trace from MCP to core, figured it could have some value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants