From $9/month

moqtap Logging

Embed MoQT session analytics in your web application. See error rates, protocol health, track usage, and latency metrics from real user sessions — at scale.

npm install @moqtap/logging
app.ts
import { initLogging } from '@moqtap/logging'
// Initialize once — starts collecting automatically
initLogging(({ apiKey: 'your-api-key' })

What you get

Client-side MoQT analytics that tell you how your protocol implementation is performing for real users.

Session statistics

Track connection duration, message counts, subscription lifecycle, and object throughput across all MoQT sessions on your site.

Error rates & diagnostics

Monitor protocol errors, failed subscriptions, unexpected disconnections, and malformed messages. Get error breakdowns by type and frequency.

Track usage analytics

See which namespaces and tracks are most active, subscriber counts per track, and publishing patterns over time.

Protocol health

Detect protocol-level problems: draft version mismatches, unsupported features, relay compatibility issues, and degraded connections.

Latency metrics

Measure subscribe-to-first-object latency, control message RTT, and inter-object gap — from the client's perspective, at scale.

Drop-in integration

Install the npm package, add a few lines of code, and start collecting data. Works with any MoQT-over-WebTransport implementation.

Logging vs Monitoring

moqtap Logging

From $9/month

Embedded in your web app. Reports from inside your users' browsers. Sees the client-side experience at scale.

  • Client-side perspective
  • Real user sessions
  • npm package integration

Performance Monitoring

Enterprise

External service that connects to your relays. Measures from the outside. Sees infrastructure health and relay performance.

  • Server-side perspective
  • Relay and endpoint probing
  • CI/CD integration

Frequently asked questions

What is moqtap Logging?
moqtap Logging is an npm package that you embed in your MoQT-powered website or web application. It collects session statistics, error rates, protocol health metrics, and track usage data — giving you production visibility into how your MoQT implementation is performing for real users.
How does it work?
Install the @moqtap/logging package, initialize it with your API key, and it hooks into your WebTransport connections to passively collect metrics. Data is sent to the moqtap cloud where you can view dashboards, set alerts, and track trends.
Does it affect my application performance?
No. moqtap Logging is a passive observer — it reads metadata from connections and messages without intercepting or modifying the data path. The overhead is negligible.
How is this different from Performance Monitoring?
Performance Monitoring is an external service where we connect to your relays and measure from the outside. Logging is an embedded SDK that reports from inside your users' browsers — giving you the client-side perspective at scale. They complement each other: Monitoring for infrastructure health, Logging for user experience.
How much does moqtap Logging cost?
moqtap Logging starts at $9/month, with pricing based on the number of sessions tracked. Contact us for volume pricing.
What data is collected?
moqtap Logging collects protocol-level metadata: message types, timing, error codes, track names, subscription states, and transport statistics. It does not collect message payloads or user content.

See how your MoQT app performs in production

Starting at $9/month. Get in touch to set up logging for your application.

Get started Email directly