OpenTelemetry alignment for logs, snapshots, and metrics in MCP Status.

Make MCP Status data portable and interoperable by aligning internal events and time series with OpenTelemetry conventions. This enables clean exports to any OTel compatible backend and makes it easier for customers to join MCP Status data with the rest of their observability stack.

Why this matters

Teams already standardize on OTel for traces, metrics, and logs. If MCP Status emits OTel friendly signals, it becomes easier to adopt, easier to integrate, and easier to trust. It also makes “capability integrity” measurable in the same language as uptime, latency, and errors.

Scope

• Snapshot events and probe run events as structured logs

• Metrics
  Synthetic health metrics and probe metrics as OTel metrics with stable naming and units

• Traces
  Optional but recommended. Each run becomes a trace with spans for transport, auth, handshake, list tools, tool call, resource read, prompt evaluation, and validation steps