{"version":"2.1.299","anchor":"otlp-metrics-endpoint-allowlist-and-ccr-get-retry-refactor","canonical_anchor":"otlp-metrics-endpoint-allowlist-and-ccr-get-retry-refactor","heading":"OpenTelemetry metrics are sent to the customer endpoint only in some cases","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/otlp-metrics-endpoint-allowlist-and-ccr-get-retry-refactor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### OpenTelemetry metrics are sent to the customer endpoint only in some cases\n\nClaude Code now sends telemetry metrics to the customer metrics endpoint only when a check allows it; logs still go to the customer logs endpoint\n\n**Unclear.** It is not clear what decides whether metrics go to the customer metrics destination.\n\n**What**\n\nClaude Code can export usage data using OpenTelemetry (a standard format for sending logs and metrics to monitoring tools). The list of destinations it sends to has changed:\n\n- Logs go to the customer logs destination, as before.\n\n- Metrics go to the customer metrics destination only when a check allows it, and always to the general metrics destination.\n\nBefore, the customer destination was always included for both. An internal retry routine for remote requests was also split in two.\n\n**Why**\n\nThis affects where session metrics end up if you collect Claude Code telemetry.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}