WebRTC gives you every tool to watch your calls, then collects nothing

1 Aug 2026 · 2 min

Watch on YouTube

1:42

The speaker explains that WebRTC includes a powerful built‑in statistics API (get_stats) that provides real‑time metrics for every call—packet loss, jitter, round‑trip time, bitrate, resolution, freeze counts, and more. However, WebRTC does not automatically store, forward, or visualise any of this data; once a call ends the metrics disappear. This creates a blind spot for teams that assume observability is handled for them. The speaker warns that without a custom pipeline to poll, ship, and persist these stats, developers will have no historical data to diagnose quality complaints, leading to angry customers and repeated issues. The core message is that while WebRTC supplies the observability tools, the responsibility for collecting and retaining the data lies entirely with the implementer, and this should be built proactively.

Chapters

WebRTC hands you every tool you need to observe your own calls, and then it collects exactly none of it for you. You are blind by default, and most teams find that out the hard way in production. Here's the trap: get_stats is incredibly rich. Packet loss, jitter, round trip time, bitrate, resolution, freeze counts, and a lot more. It's all there, updated in real time for every call in every peer connection and every stream. The observability is built right in, but WebRTC doesn't store any of it. It doesn't send it anywhere. The moment the call ends, the data is gone. No dashboard, no history, no what happened on that call yesterday unless you build that pipeline to grab it, poll it, ship it, and store it, you have nothing. And that's the gap nobody plans for. The quality complaints come in, you go check, and there's no data to check. Every future call is instrumented perfectly only if you do that. Every past call is a black hole because you never collected anything. Observability isn't the hard part. WebRTC already gave it to you. The collection is a part you own. Build that before you need it, not after the first angry customer. Every tool is right there collecting nothing. That part is on you.