{"version":"2.1.234","anchor":"more-detail-in-existing-telemetry-events","canonical_anchor":"more-detail-in-existing-telemetry-events","heading":"More detail in existing telemetry events","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/more-detail-in-existing-telemetry-events","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### More detail in existing telemetry events\n\nSeveral internal reports gained detail, including dropped event batches and whether a live artifact was adopted.\n\n**What**\n\nSeveral events gained fields: the byte watchdog now reports how long it slept, how many bytes arrived and time to first byte; internal event batches dropped after a 4xx are counted and exposed so a flush can confirm it landed; the session-memory viewer close event adds an unrated count; the device bridge start event adds where the account came from; artifact hand-off events record whether a live artifact was adopted or undisclosed.\n\n**Evidence**\n\n`cli_worker_internal_events_4xx_dropped`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}