moqtap Insight
Production MoQT telemetry. The debugger tells you what one session did on your desk; Insight tells you what your viewers' sessions are doing in production.
The collector is published on npm as @moqtap/collector. Every workspace gets Insight on the Free plan.
How it works
-
1
The collector runs in your player
@moqtap/collector sees every WebTransport MoQT session in the page, with no change to your player code. Per track, it reports throughput, object and group cadence, stalls, gaps, duplicates, out-of-order arrivals and control-exchange latency.
-
2
Sessions go to moqgest.com
The collector uploads only to moqgest.com, the ingest address. One connect-src entry in your Content Security Policy covers it. You can point it at your own ingest instead.
-
3
Insight reads them in the portal
Insight is in the moqtap portal, on the same account as your traces and shares. It opens on what changed, shows session health, and goes down to one session in detail.
In the portal
What changed
The first screen: what changed in your sessions, hour by hour.
Health
The health of your sessions, built from what the collector measures per track: stalls, group gaps, duplicates, out-of-order arrivals and control-exchange latency.
Session detail
One session, read in the same viewer that opens a .moqtrace capture: control messages named against their draft and what the session records as wrong.
Export to .moqtrace
Export a session to a .moqtrace file and share it like any trace. The export is redacted and recorded in your audit log.
What stays on the device
- Object payloads never leave the device.
- Authorization token values are masked by default.
- Until you call init() with a key, the collector makes no network request of any kind.
- discard() drops everything and transmits nothing further, for a consent withdrawal or an opt-out.
The Free plan
- 5,000 sessions a month per workspace
- Sessions kept for 30 days
- 2 projects per workspace
- 2 ingest keys per project
- Traces exported from Insight go to your library, with its own storage
A session is one viewer's playback in one page, from its first WebTransport until the page closes or 30 seconds pass with no connection open. Each counts once, in the month it began; a page that never opens a WebTransport is not counted. Sessions over the limit still count in what changed and health, but are not listed. The allowance resets each calendar month (UTC). How sessions are counted.
Paid plans are coming: tell us what you need.