Data
Measure what customers do, not just what links report.
The useful signals already exist. They usually live in different places and don't meet.
- Probes
- Pings at rising packet sizes, per route
- Service checks
- Can a test line reach streaming, social and game services?
- Tickets
- Text grouped by app, area and time
- Device data
- Which modems run which firmware
- Speed tests
- Kept, but treated as weak evidence
The trick is joining them. "Tickets about Crave went up" means little alone. "Tickets went up, only on the new firmware, only for large packets" points at a cause.
In the demo every one of these is synthetic, with faults planted on purpose so the agents can be scored on whether they find them. See the shared pipeline.