Enterprise — cloud service

MoQT Performance Monitoring

Continuous latency benchmarks and performance monitoring for your MoQT deployment. Know when performance degrades — before your users do.

Metrics that matter

Purpose-built metrics for MoQT — not generic network monitoring repurposed for a new protocol.

Control message RTT

Measure round-trip time for SUBSCRIBE, FETCH, and other request/response pairs. Detect slow handshakes and relay bottlenecks.

Object arrival rate

Track objects per second per track. Detect drops in publishing rate, relay buffering issues, or subscriber overload.

Inter-object gap

Measure the time between consecutive objects on a track. Detect jitter and identify inconsistent delivery patterns.

Subscribe-to-first-object latency

How long from SUBSCRIBE to the first object arriving. The metric that matters most for perceived startup time.

FETCH round-trip time

Measure how long it takes to retrieve historical data. Track performance for catch-up and time-shift scenarios.

QUIC transport metrics

RTT, packet loss, congestion window, bytes transferred, and stream counts from the underlying QUIC connection.

Built for your workflow

Dashboards

Real-time visibility into all monitored endpoints. Track trends, compare periods, and drill into individual sessions.

Alerting

Set thresholds on any metric. Get notified via webhook, email, or your incident management system when performance degrades.

CI integration

Run latency baselines in your pipeline. Fail builds when performance regressions are detected before they reach production.

Related use cases

Frequently asked questions

What is MoQT performance monitoring?
MoQT performance monitoring continuously measures latency, throughput, and reliability metrics for your MoQT deployment. It tracks control message timing, object delivery rates, and QUIC transport health — giving you visibility into production performance before users notice problems.
What metrics do you track?
We track control message RTT, object arrival rate, inter-object gap (jitter), subscribe-to-first-object latency, FETCH round-trip time, and QUIC transport metrics including packet loss, congestion window, and connection-level RTT.
How does monitoring differ from the Desktop debugger?
Desktop is a manual, session-level tool for debugging. Monitoring runs continuously against your production or staging environment, collecting metrics over time and alerting you when performance degrades. It answers "is my deployment healthy right now?" rather than "what is this message?".
Can I set up alerting?
Yes. You can configure thresholds for any tracked metric and receive alerts when they are exceeded. Alerts can be delivered via webhook, email, or integrated with your existing incident management tools.
Does monitoring work with CI/CD?
Yes. You can run latency baseline checks as part of your CI pipeline to catch performance regressions before they reach production. If a commit increases subscribe-to-first-object latency by more than your threshold, the build fails.
How much does monitoring cost?
Monitoring is part of our Enterprise offering with custom pricing based on the number of endpoints and monitoring frequency. Contact us for details.

Monitor your MoQT deployment

Get in touch to set up continuous performance monitoring for your relays and endpoints.