Goal
Practice a repeatable incident-debug workflow in under 45 minutes.Scenario
Assume a report: “Peers connected, but collaborative updates looked inconsistent for a short period.”Step 1: Reproduce quickly
- Start host and app surfaces from
developer-experience/apps. - Open two windows in the same room.
- Perform 2-3 shared actions (document update, presence update, map pin).
Step 2: Capture protocol evidence
Inprotocol-inspector:
- apply
Peer lifecycle,Presence, andReplay/querypresets - export trace snippet for the reproduction window
- event ordering
- unexpected missing/extra message types
Step 3: Capture replay evidence
Inreplay-lab:
- capture pre-action snapshot
- capture post-action snapshot
- inspect with range start/size controls around suspected window
- event window differences
- signals that indicate delayed or reordered behavior
Step 4: Run operator triage checklist
Apply:operators/troubleshootingoperators/metrics-and-observabilityoperators/replay-cli
- connection lifecycle anomalies
- close codes/reasons
- suspicious timing gaps in observed events
Step 5: Write your incident note
Template:- symptom
- reproduction steps
- protocol evidence (trace snippet summary)
- replay evidence (snapshot window summary)
- probable cause
- next mitigation
Success criteria
- You can produce an evidence-backed root-cause hypothesis.
- Another engineer can replay your debug flow without additional context.