Under the hood
No documentation found
System init message can now carry cold-start timing data for hosted CCR sessions
What
The 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.
Why
This gives visibility into where time is spent during a hosted session's startup and resume process, which can help diagnose slow session starts.
Names in the bundlestartup_timing
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What "CCR" stands for and what specifically consumes this telemetry isn't stated.