{"version":"2.1.295","anchor":"third-party-telemetry-log-exporters-skipped-under-a-new-cond","canonical_anchor":"third-party-telemetry-log-exporters-skipped-under-a-new-cond","heading":"Third-party telemetry log export can now be skipped","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/third-party-telemetry-log-exporters-skipped-under-a-new-cond","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Third-party telemetry log export can now be skipped\n\nClaude Code may now skip setting up log export to your own telemetry system under an extra condition\n\n**Unclear.** It is not stated what condition now stops the log exporter being created.\n\n**What**\n\nClaude Code can send its logs to a monitoring system you run, using OpenTelemetry. Before, the log exporter was always created when this was enabled. It is now created only when an extra condition allows it, so in some cases it is skipped.\n\n**Why**\n\nIf you collect Claude Code logs this way, some setups could stop receiving them.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}