Janus + PeerMetrics

Janus monitoring and call quality debugging

Monitor Janus call quality and plugin-level session behavior without changing your normal publish and subscribe flow.

Register your Janus plugin handle with PeerMetrics to capture the peer connection data behind each call, label SFU nodes, and troubleshoot issues faster.

PeerMetrics SDK

Quick setup

  • Initialize PeerMetrics for the user and conference.
  • Register the Janus SDK integration.
  • Keep your normal call setup flow.

How it works

  1. Initialize PeerMetrics before attaching or joining the Janus plugin.
  2. Create the Janus session and plugin handle as usual.
  3. Pass the plugin handle into addSdkIntegration().
  4. Optionally label the SFU instance for clearer reporting later.
Example
const peerMetrics = new PeerMetrics({
  apiKey: 'YOUR_API_KEY',
  userId: user.id,
  conferenceId: roomId
})

peerMetrics.addSdkIntegration({
  janus: {
    plugin: pluginHandle,
    serverId: 'janus-use1-a',
    serverName: 'Janus US-East'
  }
})

Based on the PeerMetrics SDK integration docs.

Built for support and ops

Troubleshoot Janus issues with session evidence

Label SFU nodes, inspect plugin-backed session behavior, and cut down the time it takes to reproduce and explain call quality complaints.

Start with the open-source stack or get help deploying dashboards, ingestion, and instrumentation faster if you want to move quickly.

See the Janus demo Talk to us about Janus monitoring View Janus integration docs

Monitor Janus calls with session-level evidence

Give engineering, support, and operations the facts they need to understand what happened in every Janus session.
  • Session evidence for Janus products
    Replace guesswork with session evidence

    Building on Janus is already difficult. WebRTC adds network, device, and browser behavior that is hard to reason about from user reports alone.

    Give your team the call-level evidence they need to improve quality, isolate regressions, and resolve incidents faster.

  • Developer relaxing
    Spot quality patterns before they become recurring support issues

    Network conditions, devices, and client behavior change constantly. Monitor the patterns that degrade Janus calls before they become recurring support problems or engineering fire drills.

  • Happy support team
    Help support and engineering work from the same facts

    Your support team should not have to guess what happened. Share the same call diagnostics across support, engineering, and operations so handoffs stay fast and credible.