Create a New Alert
How to Create a new alert for a Website Performance Monitor
The purpose of Alerts is to get notified when something goes wrong (in terms of rendering or performance) about your website or web pages.
In the app an alert is called a monitor. There are a few ways to add one:
on the Tests page, click Create New and choose Monitor. The New Monitor dialog opens, where you pick the test under Select Test
on the same page, click Add monitor in the row of a test. The New Monitor dialog opens with that test already selected
go to the Monitors page (Monitors in the sidebar) and click New Monitor. This dialog creates a new test and its alert together: next to the alert settings you enter the monitor name, location, URL, device and schedule
Which Method to Use
- Create New, then Monitor: use this to add an alert to any test you already have, picking it from the list.
- Add monitor in a test's row: use this for a test you created earlier without an alert, or when you want to add a second alert on a different metric to a test that already has one.
- New Monitor on the Monitors page: use this when you start from scratch and want the test and its alert set up in one step. The Monitors page also lists every alert across your tests, which helps when you review everything you're watching or set up several alerts in a row.
All three ask for the same alert settings, so what you fill in is identical no matter which path you took to get there.
What You Configure Next
Whichever way you opened it, the dialog asks for the same things: whether the alert is Active, which test it applies to, which metric it should watch (see the full list of alert metrics), when you want to be notified (on first failure, on recovery, or every failing run), and which alert channels (Email, Slack, Microsoft Teams, Discord, Webhook or PagerDuty) should receive the notification. You manage channels on the Alert Channels page. For the full breakdown of each field, see understanding alert configuration.
Once saved, the alert is counted in the Monitors column next to its test and listed on the Monitors page, and you can click through to it any time to see its trigger history.