OBSERVERTC / Stats Dashboard
Stats Dashboard
Move from a reported call problem to the recorded evidence.
Stats Dashboard is ObserveRTC’s interface for investigating recorded WebRTC sessions. Browse a room, choose a call and participant, and inspect quality timelines, transport state, RTP measurements, and reported issues. It reads archived telemetry rather than replacing Client Monitor or Observer.
- 01Collect and analyze
Client Monitor reports endpoint observations; Observer processes samples.
- 02Archive telemetry
Your backend writes ClientSample JSONL files to S3-compatible storage.
- 03Investigate a call
Stats Dashboard reads the archive and presents the recorded evidence.
Start with your archive
The documented client stream layout is:
<bucket>/<roomId>/<callId>/<clientId>.jsonlUse S3-compatible storage such as AWS S3, MinIO, or Cloudflare R2. Configure access on the dashboard server; storage credentials do not belong in browser code. Follow the repository’s getting-started and storage instructions.
The dashboard is a separate Next.js application. Installing the monitoring libraries does not install or deploy it. Optional mediasoup router data supports additional SFU diagnostics; client samples alone do not provide every server-side relationship.
Versions and compatibility
Stats Dashboard 0.1.0 targets sample schema 3.7.0.
Its schema source documents a target of Client Monitor JS 4.9.0 and later with sample schema 3.7.0, plus normalization of selected older payload/reason representations. This is not a guarantee that every historical schema or native client provides all displayed fields.
See the compatibility table before choosing a producer/Observer/dashboard combination. Native C++ samples share the 3.7.0 contract, but native detector and scoring coverage is partial.
Sources: package version, sample contract, and fixture tests.