We all know how important it is to monitor your WebRTC infrastructure, especially in terms of checking what happens with PeerConnections as they come and go. Everything always works great in a lab, but things can go horribly wrong the moment you’re in the wild, and having access to data that can help you check, for instance, why a PeerConnection failed, or what caused it to perform poorly, can be truly invaluable. In Janus itself, there are historically two different ways of getting this data: Both these approaches work under the assumption we’re only interested in data collected from the…