To help you get analytics for your self-hosted LiveKit Docker image, you can take advantage of the server-side analytics and telemetry collection endpoint that's built right into LiveKit's open-source SFU. This feature lets you export real-time media analytics data—things like bitrate, frame rate, packet loss, and more—so you can use it within your own systems or dashboards. Here’s a friendly guide to get you started: 1. Set up an analytics collector: Create a service that listens on the gRPC endpoints (such as

IngestEvents

,

IngestStats

) to receive the telemetry data. 2. Configure your LiveKit server: Make sure your LiveKit instance is set up to send analytics data to your collector by adjusting the right environment variables or configuration options. 3. Use analytics data models: Check out the protobuf definitions (like

AnalyticsEvent

,

AnalyticsStat

) in the LiveKit protocol repository to understand how to parse the incoming data. 4. Analyze track-level statistics: Dive into participant and track-level details, including important metrics such as packet loss, bitrate, and network quality. Just a quick note: The Analytics API that's available for LiveKit Cloud doesn’t apply to self-hosted setups, so you’ll want to build or integrate your own analytics backend. If you’d like a hand setting up the analytics collector or parsing the data, please feel free to share your preferred tech stack. I’d be happy to provide more tailored guidance to make the process as smooth as possible for you! Sources: Announcing LiveKit Cloud | Announcing LiveKit Cloud | Announcing LiveKit Cloud | protobufs/livekit_analytics.proto | pkg/sfu/connectionquality/connectionstats.go