Overview

In this tutorial you will use media link statistics from the Client Observability API, to monitor network health — estimated downlink bandwidth, the remote publisher’s uplink estimate (when available), and which side of the connection the SDK blames when quality degrades (networkDegradationSource). The sample shows those values in an on-screen overlay so you can see them change during a live session.

Example use case: A user’s remote video stutters. Your app is already subscribed. Media link stats help you decide whether to show “Your connection looks weak” (local downlink), “The other participant’s network may be unstable” (remote uplink / degradation source), or to log both numbers for support—without parsing raw WebRTC reports.

For the complete API on Android, see Client Observability (Android).

Estimated completion time: 25 mins

Want to skip this tutorial? You can jump straight to the completed Kotlin client code in the ClientObservability folder of our Android sample app repo on GitHub. The repo includes a README with full documentation on how to run and explore the project. This tutorial focuses on the Kotlin version of the Android sample app.

Requirements

To complete this tutorial, you’ll need:

• A valid Vonage Video API account — if you don’t have one, you can sign up for a free trial
• Android Studio