{"version":"2.1.286","anchor":"3p-telemetry-dropped-event-warning-downgraded-to-debug-unles","canonical_anchor":"3p-telemetry-dropped-event-warning-downgraded-to-debug-unles","heading":"Dropped-telemetry warning only shows when telemetry is turned on","tier":"notice","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/3p-telemetry-dropped-event-warning-downgraded-to-debug-unles","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Dropped-telemetry warning only shows when telemetry is turned on\n\nThe \"Event dropped\" telemetry message is now a warning only when `CLAUDE_CODE_ENABLE_TELEMETRY` is set, and a quieter debug message otherwise\n\n**What**\n\nClaude Code logs the message `[3P telemetry] Event dropped (no event logger initialized)` when it has a usage event to send but nothing set up to send it. That message used to be logged as a warning every time.\n\nIt is now a warning only when `CLAUDE_CODE_ENABLE_TELEMETRY` is set. That environment variable switches on OpenTelemetry, a standard way of collecting usage metrics and logs. Otherwise the message is logged at debug level, the detailed level normally seen only when debugging.\n\n**Why**\n\nIf you have not switched telemetry on, you no longer get a warning about telemetry events you never asked to send. If you have switched it on, you still see the warning, because then a dropped event means something is not set up as you intended.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}