OBSERVERTC / Reference

Versions and compatibility

Match your sample schema across collection, analysis, and visualization.

The sample schema connects the components. Client Monitor produces samples; Observer processes them; Stats Dashboard reads the archived records. Use the table to choose versions that share that contract.

Sample schemaObserver JSClient Monitor JSClient Monitor C++Stats Dashboard
3.5.0————
3.6.0—4.7.0——
3.7.01.1.0, 1.2.04.8.0, 4.9.0, 4.10.0, 4.10.10.1.00.1.0

Entries identify versions that use or target that schema. — means no version is listed for that combination; it does not mean all versions are incompatible. The table lists specific versions rather than promising support for every later release.

For a new integration, choose schema 3.7.0. Stats Dashboard’s documented client target starts at Client Monitor JS 4.9.0. It can normalize selected older record formats, but that is not full support for every older schema.

Before connecting components

  • Include clientId and callId when sending samples to Observer.
  • Decode codec messages into complete samples before analysis or archiving.
  • Store dashboard client streams in its documented JSONL layout.
  • Check native client capabilities if you need detectors or scoring: a matching schema does not give every producer the same features.

See Updates for release changes and migration notes.

Source references

Version coverage varies by reference. Source revisions · Markdown source