Server Mode → Settings → Notifications lets you define which events trigger admin alerts and which channels receive them. Notifications are sent by the Panel (via opterius-queue) — no third-party monitoring agent required.
Notification Channels
Uses the SMTP credentials configured in Mail Settings. Enter the recipient address (or a comma-separated list of addresses) that should receive alert emails.
Telegram
- Create a bot via @BotFather and note the bot token.
- Add the bot to a group or send it a message to get your chat ID.
- Enter the Bot Token and Chat ID in the Panel.
Test the connection with the Send Test Message button before saving.
Slack
- Create an incoming webhook in your Slack workspace: Apps → Incoming Webhooks → Add to Slack.
- Select the channel.
- Copy the webhook URL and paste it into the Panel.
Discord
- In Discord: channel settings → Integrations → Webhooks → New Webhook.
- Copy the webhook URL.
- Paste into the Panel.
Notification Events
Each event can be enabled or disabled independently per channel.
| Event | Description |
|---|---|
| SSL certificate expiring | Fires N days before a certificate expires (configurable: 7, 14, or 30 days) |
| High disk usage | Fires when an account exceeds a disk usage threshold (configurable: default 90%) |
| Service went down | Fires when a monitored service enters a stopped or failed state |
| Backup failed | Fires when any backup job returns a non-zero exit code |
| Login from new IP | Fires when an admin account logs in from an IP not seen in the last 30 days |
| Malware found | Fires when the malware scanner detects a suspicious file |
Configuring an Event
For each event you can set:
- Enabled — on/off toggle.
- Channels — which of the above channels receive this event (any combination).
- Threshold (where applicable) — e.g., disk usage percentage or SSL days-before-expiry.
Event + channel combinations are independent. For example: SSL expiry → email + Telegram, but service down → Slack only.
Alert Deduplication
Notification alerts do not repeat every polling interval. The Panel sends one alert when a condition is first detected, then sends a follow-up only if the condition persists beyond a cooldown window (default: 30 minutes). A recovery notification is sent when the condition clears (e.g., service comes back up, disk usage drops below threshold).
Tip: Enable "service went down" on Telegram for immediate visibility — it is faster than email for on-call alerting.