WebRTC monitoring questions teams ask before they deploy
Use this page to answer common product, implementation, and deployment questions about Peermetrics.The goal is simple: reduce friction for engineering, support, and platform teams evaluating self-hosted WebRTC observability and call quality monitoring.
What this page covers
- What Peermetrics measures in production calls.
- How self-hosting and managed service compare.
- Supported WebRTC platforms and deployment patterns.
What does Peermetrics measure?
Peermetrics is built for WebRTC monitoring and call diagnostics. It helps teams inspect packet loss, jitter, round-trip time, session failures, and related call quality signals so they can explain what happened in a real user session instead of guessing from tickets.
Is Peermetrics self-hosted?
Yes. The platform is open source and designed for self-hosted deployments. Teams that want more help with rollout, scaling, or custom integrations can also work with WebRTC.ventures on a managed-service basis.
Which platforms does Peermetrics support today?
The current site includes integration pages for LiveKit, Mediasoup, Janus, Vonage, Agora, Pion, and Jitsi, but those are examples rather than the limit. Peermetrics can also integrate with native WebRTC applications and other RTC tools through the SDK-level capture approach.
For a direct native WebRTC capture example, see the basic WebRTC example in @peermetrics/sdk.
Can Peermetrics help with SIP or VoIP monitoring too?
Yes, especially for hybrid environments where SIP, VoIP, and WebRTC quality issues need to be understood together. The best-fit use case is session-level troubleshooting and root-cause analysis, not only generic telecom reporting.
Why not just rely on raw getStats output or generic observability tools?
Raw stats and infrastructure dashboards are useful, but they do not automatically translate into a session narrative that engineering and support can act on. Peermetrics is meant to bridge that gap with application-aware WebRTC analytics and troubleshooting context.
When should a team use managed service?
Managed service makes sense when time-to-value matters, when rollout is complex, or when the team would rather not own every part of monitoring infrastructure and RTC-specific operations internally.
Where should I start if I want to evaluate Peermetrics quickly?
Start with the open-source repositories, review the integration pages that match your stack, and use the use cases page to see how Peermetrics aligns with large-scale monitoring and telehealth-style production requirements.