Your homegrown getStats() collector is already out of date
A homegrown getStats() collector gets built once and patched when it breaks. Why that happens, and how to build on maintained open source.
October 26, 2026
Authors
Tsahi Levent-Levi
Maker of rtcStats
Helping companies solve their WebRTC technical and roadmap challenges | 25+ years VoIP/WebRTC expert
Most recent articles by Tsahi Levent-Levi
A WebRTC stats API for AI agents: what we changed
How we split our WebRTC stats API for AI agents: a 2 KB enrich answer next to the full analyze record, and which endpoint to call.
October 6, 2026
On-prem WebRTC analysis: the answer used to be no
Self-hosting rtcStats used to mean hosted analysis. Since v1.9, the rtcstats-enrichment server runs the analysis engine inside your own network.
September 17, 2026
What WebRTC observability actually requires
WebRTC observability is not dashboards or getStats() access. Here are the six things a system has to capture before it can tell you why a call went bad.
August 20, 2026
Voice AI evals stop at the network - just when it became more important
Voice AI evals score the STT-LLM-TTS pipeline. Two transport failures leave no mark in a transcript, and full duplex removed the slack that hid them.
August 10, 2026
Your session data shouldn't leave your VPC by default
rtcStats collects WebRTC session data inside your infrastructure. Forwarding to rtcstats.com is off by default. You choose what leaves your VPC.
July 27, 2026
You don't need another dashboard for WebRTC observability
You pull the webrtc-internals dump and scroll thousands of getStats() lines. rtcStats reads it for you and lets your data stay yours.
July 20, 2026
How to debug a webrtc-internals dump with AI
Have a webrtc-internals dump from a bad call? Upload it to rtcStats and AI finds what went wrong in under 30 seconds, or query it from Claude Code over MCP.
June 30, 2026
rtcStats vs webrtc-internals: debugging WebRTC beyond the browser tab
When webrtc-internals is enough and when it isn't: rtcStats captures and analyzes real user sessions in production, where the browser tool can't reach.
June 17, 2026
WebRTC, Compute Pressure and rtcstats
Compute Pressure is the browser's privacy-preserving CPU load signal. What it means, how to use it, and how rtcstats-js collects it with your WebRTC metrics.
April 27, 2026
Never miss a webrtc-internals dump file
Stop asking users to capture webrtc-internals manually. Use rtcstats-js with IndexedDB to store WebRTC stats locally and get dumps only when you need them.
February 9, 2026
Introducing rtcStats Observations: The WebRTC agent that sees issues before you do
Meet Observations: a set of best practices that see WebRTC issues before you do, saving you time so you can focus on what matters most.
November 17, 2025
Less is more in WebRTC monitoring
Discover the 'less is more' approach to WebRTC monitoring: collect everything but focus on what matters most for faster troubleshooting.
November 3, 2025
DIY WebRTC monitoring: rtcstats to the rescue
Learn how to build your own WebRTC monitoring solution with rtcstats. Control costs, own your data, and customize your metrics collection.
October 20, 2025
How to open and read chrome://webrtc-internals
Chrome webrtc-internals explained: how to open it in Chrome or Edge, what each section shows, the metrics behind a bad call, and how to save a dump.
October 6, 2025
Why do you need to collect WebRTC statistics on the device side?
Discover why server-side monitoring isn't enough for WebRTC and how device-side statistics collection can transform your user experience.
September 15, 2025