Set up and manage uptime checks
You’ll create an uptime check so assigned Sensors probe a target on a schedule.
Before you start
- At least one online Sensor
- The URL or host:port you want to probe (reachable from those Sensors)
- Clear naming (include environment or public URL in the check name)
Create a check
- Open Argus → Uptime.
- Click Create Check.
- Fill the form and save.
Fields that matter
| Field | What to set |
|---|---|
| Name | Short label that is obvious in incidents (for example prod-api-health) |
| Check type | Usually http; also tcp, udp, icmp, dns, tls, and others |
| URL / Host / Port | Target for that check type (HTTP uses URL and optional Method) |
| Interval | Duration string such as 30s or 1m |
| Conditions | One condition per line (for example [STATUS] == 200) |
| Sensors | Which Sensors run this check (use Select all when you want every region) |
| SLA target (%) | Optional objective such as 99.9; leave blank for none |
| Enabled | Turn off to pause probing without deleting the check |
For HTTP checks, start with GET and [STATUS] == 200 unless you need a stricter body or header condition.
Manage checks
- Edit a check to change the target, interval, conditions, or assigned Sensors.
- Disable (Enabled off) during planned maintenance so history is not flooded with expected failures.
- Reassign Sensors when you add or revoke hosts.
- Delete checks you no longer need.
You’re done when
- The check appears on Uptime with assigned Sensors.
- After one or two intervals, a recent successful probe shows (or a clear failure you expected).
If it fails
| Symptom | Fix |
|---|---|
| No sensors enrolled yet | Install a Sensor first |
| Always failing | Confirm the target is reachable from the Sensor network (firewall, DNS, TLS) |
| Condition always fails | Fix Conditions (status code, path, or expected body) |
| No probes updating | Confirm the check is Enabled and Sensors are online |