{"version":"2.1.265","anchor":"new-startup-timing-telemetry-field-on-system-init-message","canonical_anchor":"new-startup-timing-telemetry-field-on-system-init-message","heading":"New startup_timing telemetry field on system init message","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-startup-timing-telemetry-field-on-system-init-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New startup_timing telemetry field on system init message\n\nSystem init message can now carry cold-start timing data for hosted CCR sessions\n\n**Unclear.** What \"CCR\" stands for and what specifically consumes this telemetry isn't stated.\n\n**What**\n\nThe system init message sent at the start of a session can now include a `startup_timing` field carrying cold-start telemetry: named startup phases and counters related to resuming and hydrating a session. This applies to hosted CCR sessions; it's absent elsewhere.\n\n**Why**\n\nThis gives visibility into where time is spent during a hosted session's startup and resume process, which can help diagnose slow session starts.\n\n- Area: Telemetry\n- Names: `startup_timing`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}