MoQT Live Streaming Monitoring

Your MoQT-based stream is live, but you can't see performance degradation until users complain. moqtap gives you real-time visibility into streaming quality at the protocol level.

The problem

MoQT is new. Your existing monitoring stack — Grafana, Datadog, CloudWatch — doesn't understand MoQT semantics. It can tell you that a server is up and packets are flowing, but it can't tell you that subscribe latency has doubled, object delivery is jittering, or a relay is silently dropping subscriptions. By the time quality issues surface as user complaints, you've already lost viewers.

Metrics built for MoQT streaming

Not repurposed HTTP metrics. Purpose-built measurements for the MoQT protocol.

Subscribe-to-first-object latency

How long viewers wait from subscribe to first content. The metric that drives perceived startup time.

Object arrival rate

Objects per second per track. Detect drops in publishing rate or relay throughput before they become visible stuttering.

Inter-object gap

Time between consecutive objects. High jitter means inconsistent delivery — even if average latency looks fine.

Control message RTT

Round-trip time for subscribe, fetch, and other control operations. Slow control messages delay session setup.

QUIC transport health

Packet loss, congestion window, connection RTT, and stream counts from the underlying transport layer.

FETCH round-trip time

Time to retrieve historical objects for catch-up or time-shift. Critical for DVR-style viewing experiences.

Solutions

Performance Monitoring

Enterprise

Continuous monitoring with dashboards, alerting, and trend analysis for your MoQT deployment.

moqtap Desktop

Free

Debug individual sessions with real-time QUIC stats and message inspection. Great for investigating specific issues.

Frequently asked questions

How does moqtap monitor MoQT live streaming quality?
moqtap continuously connects to your MoQT relays and measures protocol-level metrics: subscribe-to-first-object latency, object arrival rate, inter-object jitter, control message timing, and QUIC transport health. These purpose-built metrics tell you about streaming quality at the protocol level — not just network-level statistics.
What's the difference between this and generic network monitoring?
Generic network monitoring measures TCP/UDP packets, HTTP response times, and bandwidth. moqtap monitors MoQT-specific semantics: subscription lifecycle, object delivery patterns, priority handling, and relay forwarding. A relay can have perfect network metrics while still delivering objects out of order or dropping subscriptions.
Can I monitor multiple relays and endpoints?
Yes. You can monitor any number of relays, publishers, and subscribers across your deployment. The dashboard shows per-endpoint metrics and aggregate views across your entire MoQT infrastructure.
Does monitoring add latency to my streams?
No. Monitoring connects as a separate observer and does not sit in the data path. Your production traffic flows normally while we measure from the outside.
Can I set alerts for quality degradation?
Yes. Configure thresholds for any metric — for example, alert when subscribe-to-first-object latency exceeds 500ms or when object arrival rate drops below a threshold. Alerts can be delivered via webhook, email, or integrated with PagerDuty, Opsgenie, or Slack.

Monitor your MoQT streams

Know when quality degrades — before your viewers do.

Contact us Email directly