Reference on ObserveRTC

Monitor catalog

Mon, 28 Sep 2026 12:00:00 +0300

Search a field or select a monitor. Each declaration links to its implementation. This catalog includes identity, context, relationships, scores and measurements; it does not label every schema field as a raw browser stat.

Versions and compatibility

Mon, 28 Sep 2026 12:00:00 +0300

Component	Examined revision	Package/source version	Meaning
Client Monitor installation/configuration	`4ae541eac3305d1cc779ff6dd703211e837a7f7b`	4.10.1	npm latest checked October 9, 2026; configuration verified against release source
Client Monitor field/formula catalog	`0f08bd5d110a4e9d53cf0486962e638c5b393c49`	4.9.1	Pinned implementation reference; not npm latest
Observer	`b4a1ccb85468c94084a89ed2c007708c14ead551`	1.0.0	Pinned implementation reference; not a claim about npm latest
Schemas	`eb7fe28062b81d6db9dfb7ca565b1fb9c88b5d17`	schema 3.7.0; generator package 3.0.0	`sources/version.txt` is the schema version

Source references

Client Monitor 4.10.1 and Observer 1.1.0 are the current npm releases checked on October 9, 2026. Install with npm install @observertc/client-monitor-js to follow the published latest tag.

Known implementation differences

Mon, 28 Sep 2026 12:00:00 +0300

Delta reset semantics

DERIVED_METRICS says zero; positiveDelta returns undefined. Source wins. Other consumers can explicitly coalesce; do not overgeneralize either direction.

Where to implement a change

Mon, 28 Sep 2026 12:00:00 +0300

Choose the owning layer

Change	Implementation and verification path
New browser field	W3C/schema definitions if appropriate → schema generation → synchronized generated types → owner monitor assignment + `createSample` → observer entity update → browser-availability tests
New local derived metric	owner monitor accept/update/getter; reset/missing/stale semantics; raw→derived unit/formula metadata; tests for counter reset, no progress and missing input; serialize only if backend needs the value itself
New client detector	Detector class with category/layer, config type, constructor defaults, correct owner registration, event payload/type, issue union, source tests/taxonomy test; independently define trigger/recovery and unavailable behavior
New score behavior	`DefaultScoreCalculator` and relevant monitor readings; component reasons and root aggregation kept distinct; verify absence/zero/continuous reason visibility
New schema field	authoritative Avro/chunk, source version/changelog, generator outputs/packages, both consumer copies, codec roundtrips and compatibility tests
New server entity behavior	appropriate Observed*.update/accept, `ObserverEvents` typed scope, lifecycle cleanup, metric reset semantics, focused source tests
New server detector	class + `AvailableCallScope`/`ObserverScopeDetectorsConfigs` + appropriate `addDetector` factory switch + index exports; explicit application registration
New structural validation	Validator + `AvailableValidatorConfigs` + `Observer.addValidator` switch; evidence-backed positive/negative/inconclusive behavior
New SFU integration	application signaling/attachments → `RemoteTrackResolverFactory`; optional server object observer; no guessed publisher linkage

Verification

Client Monitor: tests/monitors/DerivedFields.spec.ts, UnreportedRoundRecovery.spec.ts, EndedTrackStandDown.spec.ts, RemoteRtcpReportStaleness.spec.ts, detector-specific specs and DetectorTaxonomy.spec.ts, scoring specs

Specifications and source references

Mon, 01 Jan 0001 00:00:00 +0000

Use a WebRTC standard to establish the meaning of a browser measurement. Use the versioned ObserveRTC implementation to establish how the library adapts, calculates, evaluates, or serializes it. A standard’s field definition does not guarantee that a browser reports that field.