{"version":"2.1.221","anchor":"background-session-telemetry-records-how-a-session-was-attac","canonical_anchor":"background-session-telemetry-records-how-a-session-was-attac","heading":"Background-session telemetry records how a session was attached","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/background-session-telemetry-records-how-a-session-was-attac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Background-session telemetry records how a session was attached\n\nBackground session telemetry now records whether an attach was cold, spare or adopted.\n\n**What**\n\nBackground and daemon dispatch and attach telemetry now emit a `via` property describing the attach path, sanitized so only three values can ever be reported.\n\n**Details**\n\n- Allow-list is cold, spare and adopted; anything else becomes undefined.\n- The value is read from the daemon's attach ack (`Nr.op === \"attach\"`) and from the dispatch source.\n- The previous build emits no such field.\n\n**Evidence**\n\n`new Set([\"cold\", \"spare\", \"adopted\"])`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}