Server metrics like CPU and bandwidth can tell you your SFU is alive, but they fail to capture local network degradation, packet loss, or media codec issues affecting individual users. This piece provides a solid breakdown of why WebRTC observability must center on client-side telemetry via getStats() rather than just traditional infrastructure dashboards. It’s a useful read for teams looking to bridge the gap between backend uptime and actual perceived call quality.