Notifications (Delivery History)
Review a log of every alert Ionhour has sent, filter it, and confirm your team was actually paged.
The Notifications page is your delivery log. Every alert Ionhour has sent — a check or job going late or down, a recovery, an incident opening or resolving, a maintenance window starting or ending, a failed billing payment — shows up here in one running list.
Use this page to double-check your team actually got paged for an incident, after the fact. If someone asks "did we get notified about that outage?", this is where you look.
What each row shows
Every notification is a single row with:
- An icon and color indicating the kind of event and its severity (Critical, Warning, or Info).
- A title and short message describing what happened.
- The check or incident the alert relates to.
- A relative timestamp (e.g. "5m ago", "2d ago") showing when it was sent.
Unread notifications are highlighted and marked with a small dot on the left. Clicking a row marks it as read and takes you straight to the check or incident it's about, so you can see the full picture — for an incident, that includes the Escalation path card, which lists each escalation step, the channel it used, and whether that step has been sent yet or is still pending.
Looking for more detail
The Notifications page tells you that an alert went out. For more context on an incident's paging, open the linked incident and check its Escalation path card — it shows each step, the channel used, and whether it's been sent or is still pending.
Filtering the list
Filter by read status
Use the All / Unread / Read toggle at the top of the page to narrow the list down to only what you haven't seen yet, or only what you've already reviewed.
Filter by type
Use the type dropdown to show only one kind of event — for example just Check Down alerts, or just Incident Resolved notifications. Options cover checks going late, going down, and recovering, plus incidents opening and resolving. Jobs, maintenance windows, and billing notifications don't have their own entry in this dropdown yet — they still appear in the list, just not as a type you can isolate on their own.
Filter by severity
Use the severity dropdown to show only Critical, Warning, or Info alerts. This is useful when you only care about the alerts that actually paged someone, not routine informational ones.
Clear filters
Once any filter is active, a Clear filters button appears — click it to reset back to the full, unfiltered list.
Marking notifications as read
- Click any unread notification to mark it read and open the related check or incident.
- Click Mark all as read to mark every unread notification in the workspace as read in one go — this isn't limited to whatever filters are currently applied, so it clears your unread count entirely, not just the rows you're currently looking at.
- Use the refresh button at any time to pull in the latest alerts without leaving the page.
No delivery from unfiltered noise
If the list looks empty, check whether a filter is narrowing it down — an active filter combination can easily hide every notification that matches. Clear filters to confirm nothing was actually missed.
Paging through history
Notifications are listed newest first and paginated below the table. Use the page controls to move forward through older alerts, and adjust the page size if you want to scan more rows at once.
Programmatic access
If you need to pull delivery history into another system or build your own reporting on top of it, see the API reference.