Uptime monitoring with Opsgenie

Setting it up

1. In Opsgenie, add an API integration to the team that should be alerted and copy its API key.
2. In StatOSS, open the page's settings, Alerts, choose Opsgenie under "Add a destination", paste the key, and tick the EU switch if your Opsgenie account lives in the EU region. Save.
3. Press "Send a test alert" to open and close a test alert.

Opsgenie is on Hobby ($4 a month) and Pro. Email alerts are on every plan, Free included. The pricing page has the rest.

What the alert holds

The page and monitor names, the URL and the reason, with an alias keyed to the monitor so the recovery closes the alert that the outage opened. Two failed checks in a row, each confirmed from a second location, stand between a blip and an alert, so the escalation policy fires for outages and not for noise. Slow alerts open and close the same way for monitors with a slow threshold.

When an alert goes out

One alert per change of state: when a monitor goes down, when it turns slow, and when it is back, with the time, the reason, and how long it was out. A monitor counts as down after two failed checks in a row, each confirmed by a second server on another network; a single failed check sends nothing. A repeat interval sends a "still down" notice every so many minutes while an outage lasts, and nothing is sent during a maintenance window. Every kind of monitor alerts the same way: a website, an API, a port, a certificate, a cron job.