W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2012

Real-time monitoring of Client

From: Talton, John <John.Talton@ca.com>
Date: Tue, 10 Jul 2012 17:18:43 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <6915294BCCE9254586F709FB6E45F56B14CA73E8@usilms112b.ca.com>

Many of the top vendors support some way to monitor the client stack (mostly for troubleshooting scenarios) via a wide range of technologies (REST, RTCP, Netflow, etc)

Many UC monitoring product utilize this information to create rich historical and real-time diagnostic information.

Specifically, most of the clients provide MOS (or enough to calculate via eModel).   Many also provide rich Device information as well a deep dive into some of the client specific metrics.

What facilities are being built into WebRTC PeerConnection to enable this type of information.

At minimum being able to query the PeerConnection for these metrics and use a secondary channel to deliver them to the monitoring device would be useful.

Thanks for the information.


John Talton | Sr. Software Engineer
CA Technologies | 1001 Winstead Drive Office #505, Cary, NC 27513
+1.919.677.2827 (v) | john.talton@ca.com<mailto:john.doe@ca.com>

[cid:image001.png@01CD5E9B.1FB8D0C0]





image001.png
(image/png attachment: image001.png)

Received on Tuesday, 10 July 2012 19:27:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:28 UTC