Thanks — yes, there are several ways to check logs for a deployed agent in LiveKit Cloud. Below are the options and when to use each. 1) View runtime logs with the CLI • Use the LiveKit CLI command:

lk agent logs

. • To target a specific agent:

lk agent logs --id <agent-id>

. • You can list agents with

lk agent list

or find the agent ID in the dashboard. • Note: this shows logs from the newest agent instance and provides limited historical data. 2) Check build logs • Build logs (created during containerization/deploy) are available in the LiveKit Cloud dashboard and via the CLI. Use these when troubleshooting build or deployment failures. 3) Agent Observability (Dashboard — Agent insights) • If Agent Observability is enabled, open your project → Sessions → open a session → Agent insights → Logs. • Logs can be downloaded in JSON or shared. • Requirements: ◦ Observability must be enabled in your project’s Data and privacy settings. ◦ Use a supported SDK: Python 1.3.0+ or Node.js 1.0.18+. • Caveats: ◦ Logs are not real-time; they typically appear after the session ends (within minutes). ◦ Logs are retained for up to 30 days. ◦ If the agent crashes before it can upload observability data, logs may be missing. 4) Forward runtime logs to an external service (recommended for production) • Send logs to Datadog, CloudWatch, Sentry, New Relic, etc., for real-time, centralized storage and long-term retention. • This requires configuring the appropriate secrets/integration for your chosen service. If you’d like, tell me which approach you prefer (CLI, dashboard Agent insights, or external forwarding) and: • If CLI: share the agent ID you want to inspect (or I can show how to find it). • If Agent insights: confirm observability is enabled and which session you want to inspect. • If external logging: tell me which provider you plan to use and I’ll give the next steps for setup. Which would you like to do next? Sources: Where to find your Agent Logs | LiveKit | Why is my Agent insights data missing? | LiveKit