Alerts and Notifications
Alerts in the Dashboard
Active alerts appear in the Alerts panel on the Dashboard and in full on System → Alerts.
Critical alerts also reach you as they happen: a badge and list on the top bar, plus a pop-up when a new one arrives. Selecting a hardware alert takes you straight to the affected drive so you can start a replacement without hunting for it.
| Behavior | Detail |
|---|---|
| Curated | Internal and duplicate alerts are not shown. Each remaining alert carries a clear ID, a plain-language message, and a runbook. |
| Acknowledge | Acknowledged alerts are visibly marked |
| Auto-solved | An alert that stops firing is marked solved automatically and stays visible for an hour |
| Update suppression | Routine noise is suppressed while a planned software update is in progress |
Alert chips in the header are split by severity and add up to the total, including info-level alerts.
Routing Alerts Outside the Dashboard
Configure delivery under System → Notifications. Alerts can go to Slack channels and to email recipients; a single alert fans out to every enabled channel.
Slack
| Field | Notes |
|---|---|
| Deliver alerts to Slack | Per-provider switch |
| Default channel | e.g. #sds-alerts |
| Critical channel | A separate channel for critical alerts, e.g. #sds-alerts-critical |
| Slack webhook URL | Stored securely; leave blank on a later save to keep the stored value |
| Critical mention | Optionally mention a group when a critical alert fires |
Email
Register the SMTP account and the recipients. Recipient fields accept display names such as
"Doe, Jane" <jane@x.com>. STARTTLS is always negotiated, so SMTP credentials never travel in
plaintext.
Save, Then Test
- Turn on Enable external notifications
- Configure at least one provider and click Save
- Click Send test alert to verify the route end to end
The test button stays disabled until external notifications are enabled and a credential has been saved.
Current configuration is a read-only snapshot of what is stored on the server. Edits below it are not reflected there until you click Save.
Turning It Off vs. Deleting It
- Turning the master switch off stops delivery but preserves the saved configuration — turn it back on and save to resume without re-entering anything
- Delete saved configuration permanently removes the Slack webhook URL, SMTP password, and all channel and recipient settings
Support Tickets
Alert delivery is separate from support tickets. To send diagnostics to MangoBoost, see Support.