Jitsi + PeerMetrics

Jitsi monitoring for WebRTC teams

Monitor Jitsi call quality from the first join, including packet loss, jitter, and peer connection failures.

Enable PeerMetrics before Jitsi creates peer connections so every conference is captured from the start and your team can investigate issues with real session evidence.

PeerMetrics SDK

Quick setup

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

How it works

  1. Initialize PeerMetrics before creating the Jitsi conference object.
  2. Use addSdkIntegration() with wrapPeerConnection enabled.
  3. Pass your conference naming details for cleaner session grouping.
  4. Continue with the regular Jitsi join flow after the integration is registered.
Example
const peerMetrics = new PeerMetrics({
  apiKey: 'YOUR_API_KEY',
  userId: user.id,
  conferenceId: roomName,
  wrapPeerConnection: true
})

const room = connection.initJitsiConference(roomName, conferenceConfig)

peerMetrics.addSdkIntegration({
  jitsi: {
    conference: room,
    serverId: 'jitsi-us-east',
    serverName: 'Jitsi US East'
  }
})

Based on the PeerMetrics SDK integration docs.

Built for hosted or self-managed Jitsi

See what happened when Jitsi call quality drops

Capture room context, participant behavior, and WebRTC quality signals so you can investigate issues without piecing the story together by hand.

Start with the open-source SDK and self-hosted platform, or bring in deployment and integration help if you want the setup done faster.

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

Monitor Jitsi calls with session-level evidence

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

    Building on Jitsi 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 Jitsi 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.