silly-belgium-71806
12/17/2025, 4:42 PMtall-airline-16756
12/17/2025, 4:42 PMtall-airline-16756
12/17/2025, 4:43 PMRoomOutputOptions or session.output.set_audio_enabled(False)).
• Remote mute by an admin via MutePublishedTrack.
• The agent programmatically muted its own published track (TrackPublication.muted).
• Track not published/subscribed correctly (publishing/subscription issues).
• Noise suppression or voice-activity detection suppressing audio (rare for total mute).
• Observability/recording disabled, causing diagnostics to miss audio (can appear like muting).
How to detect and alert developers
• Log mute/unmute actions server-side when calling MutePublishedTrack and send an alert (webhook, Slack, PagerDuty) for unexpected mutes.
• Monitor the muted state of the agent’s output track (TrackPublication.muted) in your agent code; emit a log/event and trigger an alert when it flips to true.
◦ Example: emit a warning and push to your monitoring webhook when track_publication.muted == True.
• Enable Agent Observability so you get synced logs, traces, and transcripts and can correlate mute events in the Agent insights dashboard.
• Add health checks/heartbeats that verify audio bytes are being sent; if no audio for a configured threshold, mark unhealthy and trigger alerts via your monitoring stack (Datadog, Prometheus, etc.).
• Use server webhooks for track/participant events (e.g., track muted, participant left) and route those webhook events to your alerting channels.
Next step for me to help
• Which method do you prefer for alerts (webhooks, Slack, PagerDuty, email, monitoring tool)?
• If you want, share the agent SDK/language you use so I can provide a small code snippet to watch TrackPublication.muted and send a webhook alert. Sources: Text and transcriptions | LiveKit docs | Managing participants | LiveKit docs | Rooms, participants, and tracks | LiveKit docs | SIP troubleshooting guide | LiveKit docs | https://blog.livekit.io/streamline-troubleshooting-with-agent-observability/#/portal/signup|