OPEN-SOURCE WEBRTC OBSERVABILITY
From browser statistics to the full call picture. Collect live metrics, detect issues, and see how your real-time application performs.
TypeScript libraries · Your transport · Your infrastructure
// Start with your peer connection.
import { ClientMonitor } from '@observertc/client-monitor-js';
const monitor = new ClientMonitor();
// Add your peer connection to monitor.
monitor.addSource(peerConnection);
// Explore metrics, issues, and samples.
// Connect them to your own backend.FROM ENDPOINT TO CALL
A modular toolkit for understanding WebRTC, from a single peer connection to participants, tracks, and calls.
Start with measurements from your existing peer connection.
getStats()Read live metrics, detect endpoint issues and calculate quality scores.
Explore Client Monitor →Bring browser observations to your backend and start building the call picture.
Connect your backend →Reconstruct participants, tracks and calls. Analyze issues across endpoints.
Explore Observer →Try the live example to explore Client Monitor while a WebRTC session runs.
PROJECT NOTES
L7mp Technologies · Medium
Deploy WebRTC media servers on Kubernetes with STUNner, mediasoup, and ObserveRTC, expose media through a single IP and port, and measure the additional latency.
Read on L7mp Technologies · Medium ↗webrtcHacks
How ObserveRTC Client Monitor turns WebRTC getStats into aggregated metrics, derived statistics, and tools for diagnosing call quality issues.
Read on webrtcHacks ↗webrtcHacks
Measuring end-to-end round-trip time in peer-to-peer, SFU, and cascaded-SFU environments using ObserveRTC.
Read on webrtcHacks ↗