Get vf WebRTC egress statistics

GET 
/api/egress/stats

Use this after ingest statistics confirm that RTP is arriving but a browser does not decode, render, or remain connected. The response combines vf peer state, RTCP feedback, metadata DataChannel counters, and the latest browser RTCPeerConnection.getStats() report. Add verbose=1 for recent peer errors and all=1 to retain inactive peers.

Request

Responses

200

Per-channel and per-peer RTCP, browser decode/render, connection, and metadata DataChannel statistics.

502

A required backend command, vf, DevKit, or remote catalog service failed or returned an invalid response.