Notifications
Delivery, settings and escalation of alerts
Notifications is responsible for delivering an alert (an Incident) detected by Monitoring to you — as an email, in-app via the bell in the navigation, or both. Whether an alert occurs at all is decided entirely by Monitoring; Notifications only takes care of letting you know about it.
The notification list
Under "Notifications" in the App section you'll find the full log of every notification delivered (or still pending) to you — with its time, the incident it belongs to, its channel and its delivery status.
The filter row lets you narrow the list down by channel, status, or to "Unread only"; Reset clears all filters again. Clicking the gear button (⚙) on the right opens the settings for this page.
Notification status
- Pending — not yet delivered (e.g. an email that will be sent shortly).
- Sent — delivered successfully.
- Failed — delivery failed (e.g. an SMTP error).
- Canceled — a still-pending delivery was canceled manually, via the cancel button in the Actions column.
An in-app notification can additionally be marked as read; this also affects the unread count on the bell in the navigation (see below).
With the "View All Notifications (Admin)" permission you additionally see a Recipient column (with each user's name, not their username) and every other user's notifications, not just your own. A row that isn't your own is marked red, following the admin/staff marking convention used throughout the app.
Channels
- In-app — appears in the notification list and increments the bell in the navigation. Can be switched on or off per severity in the settings.
- Email — an email to the address stored on your account. Can also be switched on or off per severity in the settings.
Settings
The gear icon in the filter row opens a dialog where you decide, separately for each severity (Info, Warning, Critical), whether you want in-app and/or email for it.
The same settings are also available on the Account page under "Account status" → "Notifications" — both places show the same, purely personal value; the admin permission from the section above doesn't change that, everyone only manages their own preferences.
The bell in the navigation
As long as you're enabled for Notifications, a bell with a number for your unread notifications appears at the top of the navigation. Clicking it opens a short preview of the most recent entries, with View all to jump straight to the full list.
This bell is available on every page of the app, no matter where you currently are.
Escalation
For critical rules you can additionally set up an escalation policy: if an incident it produced stays open and unconfirmed past a configured delay, Notifications automatically sends an extra email — either reminding the same person again, or notifying someone else instead (e.g. an on-call account).
An escalation policy isn't set up here, but directly on the corresponding rule in Monitoring, via the button with the up-arrow icon:
- Escalate after (minutes) — how long an incident may stay open/unconfirmed before it's escalated.
- Escalate to — optional; leave empty to remind the same person again, or enter a username to notify someone else instead.
- Quiet hours start/end — an optional daily window during which escalation is delayed rather than sent immediately.
- Escalate critical incidents even during quiet hours — explicitly overrides quiet hours for critical severity, so a genuinely urgent case doesn't sit until quiet hours end.
An escalated notification appears like any other in the notification list above.