Yes — you can filter agent logs by the rooms agents were dispatched to, but you need to include room context in the logs and/or forward logs to a logging service that supports filtering. How to do it 1. Add room metadata to logs: ◦ Use

setLogExtension

to attach room name/ID or custom room context to each log entry after the room connection is established. Initial connection logs occur before room context exists, so add context once the room is available. 1. View/filter logs: ◦ In LiveKit Cloud: runtime logs with agent context appear in the Agent insights tab of the project's sessions dashboard; room context will let you correlate logs to rooms. ◦ With the LiveKit CLI:

lk agent logs

streams the newest instance’s logs but doesn’t support room-level filtering. ◦ Best option — forward logs to an external logging provider (Datadog, CloudWatch, Sentry, New Relic). Ensure your logs include the room field (name or ID) so you can filter/search by room in that service. Notes • LiveKit Cloud does not persist runtime logs long-term; build logs for the latest version are stored indefinitely. For persistent, searchable, room-filterable logs use an external logging provider. Would you like the exact

setLogExtension

snippet and where to place it in your code? Sources: How to Send Logs from the JavaScript SDK to Providers like Datadog | Agent insights in LiveKit Cloud | LiveKit docs | Log collection | LiveKit Docs