{"version":"2.1.246","anchor":"telemetry-drop-warning-is-tracked-per-host-rather-than-per-p","canonical_anchor":"telemetry-drop-warning-is-tracked-per-host-rather-than-per-p","heading":"Telemetry drop warning is tracked per host rather than per process","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/telemetry-drop-warning-is-tracked-per-host-rather-than-per-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Telemetry drop warning is tracked per host rather than per process\n\nThe dropped-telemetry warning is now tracked per host instead of once per process.\n\n**What**\n\nThe once-only warning about telemetry events being dropped with no logger initialised now lives on the per-host telemetry state next to the event sequence counter, instead of a single module-wide flag, so each host can emit it once.\n\n**Evidence**\n\n`[3P telemetry] Event dropped (no event logger initialized): `\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}