OpenTelemetry exporter for traces and metrics

[keysersoft]

Everything needed is already recorded — tool call, duration, status, upstream response — it just cannot leave the box in a standard format.

Scope

• OTLP exporter behind OTEL_EXPORTER_OTLP_ENDPOINT, off when unset.
• One span per MCP tool call, with a child span for the upstream request.
• Attributes: connector, tool, MCP server, org, status, upstream status code. No parameter values and no response bodies — this is a product whose pitch is that data does not leave your network, and a trace exporter is an easy way to break that promise by accident.
• Metrics: call count, duration histogram, error count, by tool.

Good issue for someone who has wired OTel into a NestJS app before.