{"version":"2.1.285","anchor":"opentelemetry-shutdown-flushes-another-provider","canonical_anchor":"opentelemetry-shutdown-flushes-another-provider","heading":"Telemetry shutdown now flushes an additional data source","tier":"notice","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/opentelemetry-shutdown-flushes-another-provider","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Telemetry shutdown now flushes an additional data source\n\nWhen Claude Code exits, OpenTelemetry shutdown now flushes and closes one more data source, and a broken reference is fixed\n\n**Unclear.** It is not clear which data source is the one now flushed at shutdown.\n\n**What**\n\nOpenTelemetry is the system some setups use to collect usage data from Claude Code. When Claude Code shuts down, it now flushes and closes one more data source, after waiting half of the shutdown timeout. The shutdown code previously referred to a list that did not exist on one path. The timeout is set with `CLAUDE_CODE_OTEL_SHUTDOWN_TIMEOUT_MS`.\n\n**Why**\n\nSome telemetry that may previously have been lost when Claude Code exited may now be sent before it closes.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_OTEL_SHUTDOWN_TIMEOUT_MS`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}