Add an uptime monitor
Check an address on a schedule and get an email when it goes down.
Create it
Monitoring, Create monitor, Uptime monitor.
Fill in the basics
Give it a Name, pick the Website it belongs to, and enter the Address to check, for example https://example.com/health.
Save
Click Create monitor.
Settings
| Setting | Default | Range |
|---|---|---|
| Request | GET | GET or HEAD |
| Check every | 1 minute | 30 seconds to 1 hour |
| Lowest and highest good status | 200 to 399 | 100 to 599 |
| Slowest acceptable reply | 2 seconds | Up to 10 seconds |
| Warn before the certificate expires | 14 days | 0 to 3650 days, https only |
| Body match | Off | Contains, Matches a pattern, or JSON value equals |
| Locations | Your team's home location | Up to 8 |
The address must be public: localhost, .local names and private IP addresses are refused. Body match needs GET.
The first location is included. Each extra one is $0.50 a month.
Alerts
When a monitor goes down or recovers, everyone on the team with a verified email gets an email.
A monitor is down only when every location fails and a second region agrees. A monitor with one location that fails there but answers from another region shows Late, with both facts.
Let the checks through your firewall
Every check sends these two headers:
User-Agent: BlueRadar-Uptime/1.0 (+https://app.blueradar.net/probes; check-id: m2a)
X-BR-Probe-Key: <the monitor's 64-character probe key>
check-id names the monitor (m2a is an example). The monitor's Setup tab shows its own User-Agent, the check id your logs will show, and the probe key.
Checks have no fixed addresses. To let them through a firewall or WAF, allow requests that carry your monitor's probe key.
- Probe key is shown once. Rotate probe key issues a new one and the old one stops working at once.
Pause, check now, delete
Use the buttons at the top of the monitor: Pause and Resume, Check now, and Delete monitor under the menu. Deleting removes its incident history.