ClientSample carries timestamped WebRTC telemetry from Client Monitor to your backend. It includes peer connections, browser statistics, tracks, scores, events, issues and application attachments. Observer requires both clientId and callId for ingestion.

Start with the field reference when reading samples, or generation and compatibility when changing the contract. The optional JSON and protobuf codecs compress ordered sample streams.

Engineering boundaries#

A sample is the explicit serialization contract, not a dump of every live monitor property. Events, issues, and application attachments have defined locations; track context and local DOM objects are not automatically transmitted. Check the field reference when your backend needs a particular value.

Use generation and compatibility before changing types or mixing producers and consumers. Historical schema compatibility notes remain available for stored streams; release announcements belong in Updates.

Versioned schema source.