Title here
Summary here
OBSERVERTC / Client Monitor
Detector catalog
Start with the symptom, then inspect the evidence and recovery rule.
This catalog documents 46 detector classes from the verified 4.9.1 baseline. It is not yet an exhaustive catalog of 4.10.1; current configuration includes newer audio and loopback options. Categories describe the condition; monitor ownership describes where the detector runs. An event does not necessarily open an issue, and an issue does not necessarily lower a score.
Connectivity
Connection establishment, handshake failures and path changes.
Transport Quality
Delay, loss, congestion and stalled media transport.
Pipeline Disruption
Capture, encoding, delivery, decoding and playout failures.
Perceived Quality
Visible and audible degradation, including synchronization.
Telemetry
State changes and collection-health events.
Configuration and lifecycle
Detectors run on their owning client, peer connection or track as observations arrive. Their category describes the condition being judged, rather than their owner.
Use Configuration for defaults and overrides. A detector configuration object replaces its defaults; nested values are not deep-merged. Set a detector to null to disable registration.
The category guides describe triggers and recovery. For exact comparison operators, missing-input behavior, emitted payloads and resolution paths, use the implementation reference.
Version coverage varies by reference. Source revisions · Markdown source