ObserveRTC

OBSERVERTC / Codecs

Codecs

Choose JSON or protobuf for stateful sample transport.

Both ObserveRTC codecs encode differences between successive ClientSample records. Choose JSON for readable messages and a small runtime footprint, or protobuf for compact binary payloads.

  1. 01A sample stream

    Start with samples from one monitored client.

  2. 02Encode and transport

    Use JSON or protobuf over a transport you control.

  3. 03Decoded samples

    Restore complete samples before analysis.

Optional encoding between collection and backend analysis.
Protobuf Codec

Compact binary deltas with encoding and decoding in one package.

JSON Codec

Readable JSON deltas with zero runtime dependencies.

Use one encoder and decoder per client stream. Preserve order and complete delivery; reset at reconnect or snapshot boundaries. Decode samples before passing them to Observer.

Integration boundaries

A codec compresses sample representation; it does not authenticate, deliver, or store telemetry. Each encoder/decoder maintains stream state, so do not share a single decoder between unrelated clients. Handle reconnects and missing messages according to the selected codec’s reset/snapshot contract.

Choose a format using your transport constraints and actual streams. Compression results documented in the codec pages describe their measured fixtures, not a guarantee for every deployment. Decode before passing samples to Observer.

Version coverage varies by reference. Source revisions · Markdown source