Uptime history and incidents
You’ll use the Uptime tab to see availability, SLA, and active incidents after checks are running.
Argus does not yet send email, SMS, or chat webhooks from the dashboard. Watch Argus during an outage, or use your own on-call tools and support tickets until product alerting ships.
Overview metrics
At the top of Uptime you get organization-level signals such as:
- Overall uptime across checks
- Active incidents (open failures)
Use these to see whether the problem is isolated or widespread.
Check cards and detail
Each check card summarizes the target, assigned Sensors, and recent health.
Open a check to inspect:
- Uptime history (for example the last 24 hours)
- Response-time trends
- Recent incidents for that check
- Which Sensors are assigned and how they are doing
If a check has an SLA target (%), compare observed uptime against that objective.
During an outage
- Open Argus → Uptime and note Active incidents.
- Open the failing check and confirm the failure is still open.
- Check whether every assigned Sensor fails, or only one region — that separates a target outage from a local Sensor/network issue.
- Fix the target (or pause the check during planned maintenance), then confirm incidents clear after the next successful intervals.
You’re done when
- You can find overall uptime and open incidents without guessing.
- For a known failure, you can tell which check and which Sensors are involved.
If it fails
| Symptom | Fix |
|---|---|
| Empty charts / no history | Confirm the check ran for at least a few intervals and Sensors are online |
| No incidents while the site is down | Confirm Conditions match what “up” means; confirm Sensors can reach the target |
| Expecting email/SMS alerts | Not available in Argus yet — watch the dashboard or your external on-call channel |