Facelift
We have a new dashboard and a bit of other color changes here and there, to make things a bit more uniform and readable.
The new dashboard now shows you information about the services you are using, reducing the amount of information that is not relevant to you.
For probeRTC, we are now showing in red the number of configured probes that aren’t running.
For qualityRTC, we now show the estimated number of network tests that will be conducted during the monthly cycle based on previous use during the same cycle.
Other than that, there are now more breadcrumbs to make navigating back and forth in test results easier.
Testing & Monitoring
Analysis
- From Chrome 85, outgoing simulcast channels appear as multiple channels with separate statistics in our analysis
- The scoring algorithm has been tweaked to provide more accurate results in group sessions
- Channels information has been cleaned up a bit, to show only relevant information
- Round trip graphs no longer show incoming data (which was always 0, as that data isn’t available)
- Events added using .rtcEvent() now show their name when you hover on them in the graphs
Testing
- .rtcCallWhenDone() is a new script command that enables you to create a function that will be called when testRTC wraps the test script – even if it fails prematurely
- .rtcCaptureCallData() now allows choosing the tab holding chrome://webrtc-internals. This is useful for restrictive services such as proctoring applications
- New #get-chrome-log run option was added. This is useful when trying to figure out browser behavior in some cases
APIs
We’ve introduced more metrics out of test results so you can now collect and build your own dashboards:
- /testruns/{testId}/?detailed=true now retrieves more metrics data out of a test run
- /testagents/{testAgentId}/files was added. Now you can download the collected test data such as browser log and webrtc-internals dump file
- APIs got polished a bit, some were added a few additional fields
qualityRTC: Network Testing
New tests
- We now offer Speed testing machines and TURN servers as on premise installations. If you would like to run accurate tests for your data center, then these are now available
- There’s a new Video P2P test available. Watch this quick video to see how it works:
New features
- We’ve optimized how we load the qualityRTC page for our users
- The page is now considerably smaller in size and faster to load
- We now load only the pieces of tests you need and do that on demand
- We can now configure a webhook for tests conducted in qualityRTC
- The webhook will be invoked whenever a test was executed, or when certain test result thresholds are met (warnings or faulty results)
- A JSON blob with all metrics collected is provided (more details here)
- This means you can now collect and analyze that data within your own BI environment
- Alert thresholds are now available. Up until now, you either received an email on each test conducted or never. You can now receive such an email only if certain threshold conditions are met
- BI/Analytics table has been improved
- If new tests are available, they will now be indicated on a new refresh button
- You can now search for a specific network test result based on its id
- Added the IP address, so you can group or search by it
- Grouping now shows averages on metrics collected
- PDFs created by end users now include the date and id of the test
- qualityRTC now enforces the retention period. This makes retrieval of data and analysis run faster
- Added more thresholds to the values as well as the ability to customize them to the values suitable for your application
probeRTC: Zero install network probes
- Alert thresholds are now available. When the probe’s results are within the acceptable limits you can now configure it to send out an alert email
- We’ve created a new explainer video about this product