With multi-location Synthetics alert conditions, you can set up a Synthetics monitor to notify you when a specific number of locations are failing at the same time.
Why use multi-location alert conditions?
For Synthetics monitors that run in multiple locations, a single location will sometimes temporarily fail for a wide variety of reasons. In many cases, a single, short-lived failure does not indicate a problem that would require an alert notification.
With multi-location alert conditions, you can set the number of locations that must be simultaneously failing in order to trigger a violation and send you a notification. For example, if your Synthetics monitor is running in six locations, you might set a condition requiring four locations to fail for you to receive a notification.
|Required check frequency||15 minutes or less.|
|Maximum locations per condition||50|
|Conditions per account||This feature has a limit of 1000 conditions per account, but some types of Infrastructure alert conditions also count towards this limit. If you get a notification that you've exceeded your limit, contact your account representative or Support for assistance.|
|Status between checks||A failed location check will be considered failed until it performs a successful check. For example: a location may fail and then immediately become available, but New Relic will consider it failed until a scheduled check is reported as successful.|
Here's a diagram that shows how a four-location alert condition will be triggered for non-simultaneous failures:
Create condition from Alerts UI
Before creating a condition, read the rules for multi-location alert conditions.
To set up a condition via the UI:
- From alerts.newrelic.com, start the Create a condition process.
- Select Synthetics > Multiple location failures.
Create condition with the API
Before creating a condition, read the rules for multi-location Synthetics alert conditions.
To use the Alerts REST API to manage multi-location Synthetics alert conditions, use the REST API explorer.