{"version":"2.1.283","anchor":"in-remote-sessions-otlp-metrics-can-go-through-the-session","canonical_anchor":"in-remote-sessions-otlp-metrics-can-go-through-the-session","heading":"Metrics from cloud sessions can be sent through the session's own connection","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/in-remote-sessions-otlp-metrics-can-go-through-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Metrics from cloud sessions can be sent through the session's own connection\n\nIn remote sessions, usage metrics can now go to the session's own metrics address, signed with `CLAUDE_CODE_SESSION_ACCESS_TOKEN`\n\n**What**\n\nClaude Code can send usage metrics using OpenTelemetry, a standard format for reporting them. In a remote session (one running on a server rather than your computer), it now has another route for them. It is used when all of these hold:\n\n- `CLAUDE_CODE_REMOTE` is set\n\n- `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` exactly matches the session's own metrics address, built from `SESSION_INGRESS_URL` and `CLAUDE_CODE_REMOTE_SESSION_ID` and ending in `\/worker\/otlp\/metrics`\n\n- no OpenTelemetry headers are configured\n\nMetrics then go to that address, signed with `CLAUDE_CODE_SESSION_ACCESS_TOKEN`. This route is checked before the existing route that uses `ANTHROPIC_BASE_URL`.\n\n**Why**\n\nMetrics from cloud sessions can be collected using the session's own credentials, without separate ones.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}