Best practices in using rtcStats
Get to know what are the most powerful ways to use rtcStats to improve your WebRTC application development and deployment.
At the heart of rtcStats is the ability to upload WebRTC metrics, be it webrtc-internals or an rtcstats file and have it analyzed. The end result is you being able to troubleshoot and debug your ticket in minutes instead of hours.
Here's the thing though - rtcStats can do A LOT more than that.
Here, we go over some tried and true tips and best practices for getting the most out of rtcStats for different workflows you may have in your company. The approaches below are ordered by maturity - start where you are today and grow from there:
| Approach | Best for | Effort |
|---|---|---|
| Ad-hoc debug and troubleshoot | Getting started, one-off investigations | None - just upload a file |
| Passive complaint handling | Teams with 100+ monthly sessions who want to investigate any session on demand | Some engineering and DevOps setup |
| Active observability | Production deployments with 100K+ sessions wanting full monitoring and trend analysis | More engineering and DevOps investment |
Check them out and see what fits you best.