Alerts are configured individually for each test, in the test settings.
A Performance test alert is triggered when the test performance meets the conditions configured in the alert, based on how the test performs for each test cycle (test frequency). You can configure the frequency for Backbone tests. Private Last Mile and Mobile tests have a fixed frequency. When a test returns to Good status and remains Good for one test cycle, an Improved alert is triggered so you know the issue that triggered the original alert is resolved.
For Availability tests, the configuration details include the alert threshold, the alert level, and the destination.
An Availability test alert is triggered when the test failures exceed the thresholds configured in the alert; or, for an Improved alert, when the test performance returns to normal for the test cycle.
Alerts are not triggered for inactive measurement locations.
When an alert is triggered, it is recorded in the Alert log, besides being sent to the configured destinations.
To create effective alerts, plan your alerts in the context of your overall monitoring strategy. For details, see Getting Started with Alerting.
For details of configuring alerts, see the help page for the appropriate test type: