{"version":"2.1.307","anchor":"otlp-metrics-exporter-wrapped-in-a-scoped-resource","canonical_anchor":"otlp-metrics-exporter-wrapped-in-a-scoped-resource","heading":"OpenTelemetry metrics export is set up a little differently","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/otlp-metrics-exporter-wrapped-in-a-scoped-resource","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### OpenTelemetry metrics export is set up a little differently\n\nWhen metrics are sent over OpenTelemetry by gRPC or HTTP protobuf, Claude Code now prepares an extra resource before creating the exporter\n\n**Unclear.** It is not known what the extra step does or whether exported metrics look any different.\n\n**What**\n\nOpenTelemetry is a standard for sending usage metrics to a monitoring system you run. Claude Code can export metrics this way using the protocol you choose with `OTEL_EXPORTER_OTLP_METRICS_PROTOCOL`. For both `grpc` and `http\/protobuf`, it now prepares an extra resource before it creates the exporter.\n\n**Why**\n\nThis may change how metrics export is set up.\n\n- Area: Telemetry\n- Names: `OTEL_EXPORTER_OTLP_METRICS_PROTOCOL`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}