Notifications
A panel that only shows problems on a dashboard tells whoever happens to be looking. XUI.live pushes: 33 events, each individually switchable, delivered to Telegram, a webhook, or both — so the panel tells you before a customer does.
Open Notifications.
The channels
Telegram — a bot token and a chat ID; alerts land in your phone, or in an ops group where the whole team sees them.
Webhook — a URL that receives each event as JSON, for Discord, Slack, a ticketing system or your own automation.
A test send proves the wiring end to end before you depend on it.
The events
Eight categories, each with its own switches:
- Server — offline and back online, disk space, high CPU, RAM and load, server added.
- Backup — succeeded, failed. The failure alert is the one that earns its keep.
- Streams — stream down, back online, recording done or failed.
- Subscribers — line created, deleted, banned, expired, expiring soon, connection limit hit.
- Resellers — logins, credits added, balance running low.
- Security — admin logins and failures, login floods, IPs blocked, restreams detected, 2FA changes.
- Support — new tickets and replies.
- System — SSL renewed, licence expiring.
Switch on what you would act on and leave the rest off — an alert channel that cries wolf gets muted, and then the real alert dies in the noise. A sensible starting set: server offline, backup failed, stream down, restream detected, licence expiring.
The same events also feed the panel’s own notification bell; Telegram and the webhook are for the hours you are not looking at it. And for everything quieter than an alert, the dashboard is next.