Client Monitor on ObserveRTC

What changed in 4.9

Sun, 13 Sep 2026 10:00:00 +0200

4.9.0 is the largest release the library has had. It is worth reading before upgrading, because several changes fail loudly (a retired config key no longer type-checks) and a few change behaviour quietly (the collection period is 2.5× longer by default, so tick-counted detectors take 2.5× as long to fire).

Integrations

Thu, 07 Sep 2023 16:33:54 +0200

The monitor collects nothing until you give it a source. A source is anything that owns RTCPeerConnections: a peer connection itself, a mediasoup Device, or a single mediasoup transport.

Configuration

Thu, 07 Sep 2023 16:33:54 +0200

ClientMonitorConfig is entirely optional — new ClientMonitor() runs on defaults. Every detector reads a block named after itself, its name in camelCase, and reads nothing else.

Detectors

Thu, 07 Sep 2023 16:33:54 +0200

“The call was bad” is not a diagnosis. The library ships 46 detector classes raising 37 issue types, grouped into five categories, so that an engineer reading a failed session knows which of four completely different investigations to start — and which facts to read alongside them.

Connectivity detectors

Sun, 13 Sep 2026 10:00:00 +0200

This is the reference for category 1. It exists because the alternative is five issue types that all mean approximately “ICE didn’t work”.

Transport quality detectors

Sun, 13 Sep 2026 10:00:00 +0200

This is the reference for category 2. It exists because “the network is bad” is four different faults with four different fixes, and until 4.9.0 the library could only name one of them.

Pipeline disruption detectors

Sun, 13 Sep 2026 10:00:00 +0200

This is the reference for category 3, the largest at 15 classes and 15 issue types. The answer it is built to give is a place: the boundary where the upstream counter advanced and the downstream one did not.

Perceived quality detectors

Sun, 13 Sep 2026 10:00:00 +0200

This is the reference for category 4, asked from the participant’s chair rather than the engineer’s. Nothing here says where the media chain broke, and nothing here has to.

Telemetry detectors

Sun, 13 Sep 2026 10:00:00 +0200

This is the reference for category 5. Nothing here judges the call. What it buys is the missing column in most investigations: which codec the bad calls were using, when the layer stopped being sent, whether the path moved just before the complaint.

Events & issues

Thu, 07 Sep 2023 16:33:54 +0200

ClientMonitor emits two categories of notification: issues, which describe a problem state, and events, which describe a thing that happened. Picking the right one is the key to keeping alerting code sane.