Collaboration in rtcStats
How to use rtcStats in larger teams as well as with external users who need access to the data.
rtcstats.com is designed for use by teams.
Let's face it - reviewing webrtc-internal dump files is usually a team sport:
- The user generates a file for you (hopefully, automatically using our rtcstats-js client SDK)
- Your first line of support person reviews the dump file, deciding what the issue is
- They then write an internal support ticket, which passes to the engineering team
- A developer from engineering will likely review the dump file, maybe even making a fix in the application
- The testing team will need to test any fixes made before they get deployed. It might be useful for them to have access to that same dump file that was the original cause of the fix in the first place
Throughout this process, multiple stakeholders needed to access that webrtc-internals dump file, each looking at it from his own angle, with his own specific needs.
Because of this, we've made sure rtcstats.com is highly tuned to your needs and the collaborative nature of your work. Here are a few ways in which you can collaborate with the many stakeholders around a WebRTC issue.
rtcStats support for multiple users per account.
Leaving comments on WebRTC dumps in rtcstats.com.
Sharing a WebRTC dump publicly with non-users in rtcstats.com.