{"version":"2.1.271","anchor":"remote-bridge-session-start-telemetry-gained-a-ccr-session-i","canonical_anchor":"remote-bridge-session-start-telemetry-gained-a-ccr-session-i","heading":"Remote-bridge session-start telemetry gained a ccr_session_id field","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/remote-bridge-session-start-telemetry-gained-a-ccr-session-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Remote-bridge session-start telemetry gained a ccr_session_id field\n\nRemote bridge session-start telemetry now includes a ccr_session_id field\n\n**What**\n\nThe `tengu_bridge_repl_started` telemetry event, recorded when a Remote Control bridge session starts, now includes an additional `ccr_session_id` value derived from the bridge session's ID, alongside the fields it already recorded.\n\n**Why**\n\nThis is an internal telemetry addition that helps correlate bridge session activity by ID; it doesn't change any user-facing behavior.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}