https://livekit.io logo
Join Slack
Powered by
Why does the livekit cloud web application show di...
# ask-ai
g
Why does the livekit cloud web application show different data than the livekit cli?
t
Thanks for reaching out, Daniel. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The LiveKit Cloud web application and the LiveKit CLI may show different data due to configuration or authentication differences. Here are some possible reasons: • Configuration Differences: The CLI requires environment variables (
LIVEKIT_URL
, 
LIVEKIT_API_KEY
, and 
LIVEKIT_API_SECRET
) to connect to LiveKit Cloud or a self-hosted server. If these are not correctly set or point to different instances, discrepancies can occur. • Authentication: Mismatched API keys or secrets between the CLI and the web application can lead to different data being displayed. • Data Synchronization: The CLI may show outdated or incomplete data if it is not properly synchronized with LiveKit Cloud. • Feature Parity: Differences in how the CLI and web application fetch and display data might also cause inconsistencies. To resolve this, ensure the CLI's environment variables match the web application's configuration, verify both are accessing the same LiveKit instance, and check for synchronization issues. Let me know if you need further assistance! Sources: Accepting incoming calls | LiveKit Docs | Accepting incoming calls | LiveKit Docs | Accepting incoming calls | LiveKit Docs
g
The configuration and authentication is correct. The CLI appears to show correct and up to date data. However, the cloud web application shows outdated information. It can take up to half an hour for the web application to show data.
t
Hey there! If you’re noticing a delay in the LiveKit Cloud web app showing updated data, no worries — here are some friendly tips to help speed things up: • Upgrade to Analytics V2: Make sure you’re on the latest analytics system. It’s designed to load faster and refresh data live, so you get updates quicker. • Optimize Update Frequency: If you’re updating participant attributes a lot, try using data packets instead. This can help cut down on any sync delays. • Use WebRTC: For real-time data, WebRTC is your friend since it reduces latency more than WebSockets. • Verify Configuration: Double-check that your app is using the latest LiveKit SDK and following best practices for real-time syncing. • Check Refresh Intervals: With Analytics V2, you can set how often data refreshes. Make sure this fits what you need. If you want, I’m here to help you walk through any of these steps — just let me know! Sources: Participant attributes and metadata | LiveKit Docs | Participant attributes and metadata | LiveKit Docs | CHANGELOG.md | Capturing metrics | LiveKit Docs | Say hello to improved Cloud analytics
Open in Slack
PreviousNext
Powered by