Uptime Monitoring: Alerts
Overview
Use this page to review active and resolved uptime alerts. An alert is a failure record created when one of your uptime checks fails: it captures the failure reason and stays active until the check recovers, or you resolve it by hand. Alerts give you one place to see what is currently down and to review past outages without checking each monitor separately.
Alerts depend on checks already configured on Uptime Monitoring: Checks: without a check that has failed at least once, there is nothing to show here. Each alert traces back to the incident the appliance recorded, so the actual resolve action happens on Uptime Monitoring: Incidents, not on this page. From an alert you can also jump straight to the check that raised it.
This page lets you filter alerts with the All, Active, and Resolved tabs, search by check name, and read each alert's failure reason with Triggered and Resolved timestamps. The Active, Resolved, and Total tiles give an at-a-glance count, and Refresh reloads everything from the latest data.
Key concepts
- alert - A failure record created when an uptime check fails. It stays active until the check recovers on its own, or until you resolve it by hand. (related: Uptime Monitoring: Checks)
- check - A monitor that tests a service, URL, or server on a schedule; a check failing a test is what creates an alert here. (related: Uptime Monitoring: Checks)
- incident - The underlying failure record the appliance keeps for each check failure. Alerts are read from incidents, and resolving an alert by hand is an action you take on the incident, not on this page. (related: Uptime Monitoring: Incidents)
When to use it
- To see which uptime checks are currently failing and need attention
- To review past outages, including how long each one lasted
- To get an at-a-glance count of active versus resolved failures from the Active, Resolved, and Total tiles
- To find the alert history for one specific check using Search
- To jump to Incidents to manually close an alert that hasn't recovered on its own
- To open the check behind an alert so you can review or adjust its configuration
Before you begin
- At least one uptime check exists, created on Uptime Monitoring: Checks
- That check has failed at least once; a check that has never failed produces no alerts to review
- To resolve an alert by hand rather than wait for the check to recover, your account needs permission to resolve incidents, checked on Uptime Monitoring: Incidents
Common workflows
Investigate and close out an active alert
Persona: load-test operator or admin
- Select the Active tab.
- Expect: The list filters down to the currently active alerts; the tab's badge count matches the Active tile.
- Select View Check on the alert you want to investigate.
- Expect: The related check's page opens, showing its configuration and recent run history.
- Return to Alerts and select the Incidents link.
- Expect: The Incidents page opens, where you can resolve the underlying incident by hand.
Verify: After resolving the incident, select Refresh on Alerts: the alert moves out of the Active tab and into Resolved, and the Active tile count decreases by one.
Review the alert history for one check
Persona: load-test operator or admin
- Type the check's name into Search.
- Expect: The list filters to only the alerts raised by that check as you type.
- Select Refresh.
- Expect: The filtered list reloads with the latest alert data for that check.
Verify: Only alerts matching the searched check name remain visible, each with Triggered and Resolved timestamps showing that check's full failure history.
Steps
Step 1
Open Alerts under Monitoring and Uptime.
Expected result: The Uptime Alerts page loads with the Active, Resolved, and Total tiles above the All, Active, and Resolved tabs, and the full alert list below them.
This is the starting point for seeing which uptime checks are currently failing and for reviewing past outages.
- The All tab is selected by default, showing every alert regardless of state.
- The Search field filters the list by check name.
- Each alert card shows a Failure chip and, once recovered, a Resolved chip with Triggered and Resolved timestamps.
Tabs on this page
-
All - Shows every alert regardless of state, both alerts still active and alerts that have since resolved.
- Full alert list with Search; this is the default view when the page loads.
-
Active - Shows only alerts whose check has not yet recovered; the badge count matches the Active tile.
- Same card layout as All, filtered to active entries; these rows have no Resolved chip or Resolved timestamp.
-
Resolved - Shows only alerts whose check has recovered, or that were resolved by hand on Incidents.
- Same card layout as All, filtered to resolved entries; each row carries a Resolved chip and a Resolved timestamp.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Search | Filters the alert list to checks whose name matches the text you type, so you can find one check's alert history without scrolling the full list. | free text | No | empty |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Check name | - | Names the check that raised the alert; matches the check's name on Uptime Monitoring: Checks. |
| Failure chip | - | Always shown, since every row on this page is a check failure; it has no other value. |
| Resolved chip | - | Shown only once the check has recovered; an alert without this chip is still active. |
| Failure reason | - | The error the check recorded when it failed; use it to tell a timeout apart from a DNS failure or another cause before you investigate further. |
| Triggered | - | When the check first failed and the alert became active. |
| Resolved | - | When the check recovered or the alert was resolved by hand; compare it to Triggered to see how long the outage lasted. Blank while the alert is still active. |
| Status icon | - | A small marker next to the check name showing the alert is a failure record; every alert on this page carries the same failure styling. |
| Active tile | - | The number of alerts currently active across all checks; matches the Active tab's badge. |
| Resolved tile | - | The number of alerts that have recovered or been resolved by hand. |
| Total tile | - | The combined count of active and resolved alerts; equals Active plus Resolved. |
Controls reference
Refresh
Reloads the alert list, the Active/Resolved/Total tiles, and the tab badges from the current data.
When to use: After resolving an alert on Incidents, or after enough time has passed for a check to run again, to confirm the counts are current.
Side effects: Read-only: it only reloads data on screen, it does not change any alert or check.
Incidents
Opens the Incidents page.
Side effects: Read-only navigation; the resolve action itself happens on Incidents, not here.
View Check
Opens the check that raised the selected alert.
When to use: When an alert's failure reason or repeated occurrences make you want to review or adjust that check's configuration.
Side effects: Read-only navigation; it does not change the alert or the check.
Try again
When to use: When the page shows a read-failure message instead of the alert list and tiles.
Side effects: Read-only retry; no alert or check data is changed.
Clear all
Clears the Search text and returns the state filter to All.
When to use: After narrowing the list with Search or a tab, to quickly return to the full alert list.
Side effects: Read-only: it only changes which alerts are displayed, not any underlying data.
Verify the result
When the page loads correctly, the Active, Resolved, and Total tiles show numbers rather than a blank state or an error message, and the list below shows one card per alert with a check name, a Failure chip, and a Triggered timestamp. An alert that has recovered also shows a Resolved chip and a Resolved timestamp; one that is still active shows neither. If the list looks shorter than expected, check whether a tab filter or text in Search is narrowing the view before assuming the data is wrong. An empty list with no error message means no alerts match the current filter, not that the read failed.
Troubleshooting
- Symptom: The page shows a failure message instead of the alert list. Fix: Select Try again; a failed read is always shown as an explicit error here, never as an empty list.
- Symptom: The Active, Resolved, and Total tiles show no numbers.
- Symptom: There's no way to close an alert from this page. Fix: Select the Incidents link and resolve the alert there; this page only displays alerts, it does not resolve them.
- Symptom: An alert you expect to see is missing. Fix: Check which tab (All, Active, Resolved) is selected and clear any text in Search, since both narrow the list.
- Symptom: The Active tab's badge count doesn't match the Active tile. Fix: Select Refresh to reload both from the same data; they should always match afterward.
Related articles
- Prerequisite: Uptime Monitoring: Checks - checks must exist and fail before they raise any alert shown here
- Next step: Uptime Monitoring: Incidents - resolving an alert by hand is done on Incidents, not on this page
- See also: Uptime Monitoring: My dashboard - gives a broader at-a-glance view of uptime status alongside alert counts