Ad-hoc debug and troubleshoot

The most common use of rtcStats is for ad-hoc troubleshooting and debugging of WebRTC problems.

Storyline

The storyline goes something like this:

1. You get a complaint from a user, your QA team or bumped into a bug yourself
2. Now you ask for a webrtc-internals dump file to be generated and sent your way
3. After a bit of a back-and-forth, you get that webrtc-internals file
4. Upload it to rtcstats.com and you can easily figure out where the issues are

NOTE: On one of our paid plans, you will also have Observations and AI summaries, which will reduce your time to get to the root cause drastically. If you are interested in trialing these features, do let us know

Reasoning

Let's review quickly what are the advantages and challenges of this approach:

Advantages

• No upfront effort. There is nothing you need to do to get started. The only thing needed is to open an account on rtcstats.com
• It doesn't change your current workflow. You still use webrtc-internals dump files to investigate issues. Now you just upload them to rtcstats.com instead of opening them in a text editor

Challenges

• Obtaining webrtc-internals dump files is still a hassle, especially for issues reported by end users

Our suggestion

Start with this approach when trialing the use of rtcStats.

Since there's little in the way of upfront investment, and you can use the free plan, you should get the gist of what rtcstats.com can do for you.

In the same way, if you're not sure, but want to understand better the differences, reach out to us to get access to a trial paid Developer plan so you can experience the magic of using our Observations and AI summaries capabilities. They are the true game changer for the ad-hoc troubleshooting and debugging workflow.

As a first step, you can store rtcstats data to the browser's IndexedDB and pass it along to rtcstats.com only when needed. Read here on how to implement that quick hack: Never miss a webrtc-internals dump file