title | tags | translate | metaDescription | redirects | freshnessValidatedDate | |||||
---|---|---|---|---|---|---|---|---|---|---|
Alerts for synthetic monitoring |
|
|
New Relic can use alerts to notify you about synthetic monitors's failures. |
|
never |
If you want to receive alert notifications when a synthetic monitor fails, you can configure the alert notification after you have created one. You can configure your monitor's alert condition via the alerts UI.
To identify which monitors [do not have conditions](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) assigned to them, review their color-coded health status.A monitor can be included in multiple alert policies and conditions. You can view the alert policies and conditions for the selected monitor from the UI.
To add an existing monitor to an alert policy:
- Go to one.newrelic.com > Alerts > Alert policies.
- From the list of existing alert policies, use the search box or scroll the list to locate one or more alert policies where the monitor has not already been added.
- Open the policy, then click + New alert condition.
- Click Use guided mode.
- Click Synthetic monitors and then click Next.
- Select your synthetic monitor from the list, select the metric to monitor, and then click Next.
- Fill out the remaining settings and click Next.
- Name your alert condition, set additional optional settings, and click Save condition.
To remove an existing monitor's alert condition from an existing alert policy:
- Go to one.newrelic.com > Alerts > Alert policies.
- From the list of existing alert policies, use the search box or scroll the list to locate and select an alert policy where the monitor has an alert condition that has already been added.
- Select Delete from the action menu for the alert condition.
Synthetic alert monitors operate on a three-strike basis, registering a failure only after three monitor attempts from a single location return an error. Your alert policy configuration and notification channel settings will determine when you receive notifications for specific monitors and locations.
If you monitor a non-public app and add your selected public minion IPs to your allow list, you may very infrequently receive a false downtime alert. When a synthetic monitoring data center goes down, New Relic may decide to temporarily use an alternate host, which results in the temporary server's IP being blocked by your app.
The muted monitor status will be removed on [February 29, 2024](https://forum.newrelic.com/s/hubtopic/aAX8W0000015BHc/endoflife-product-updates-july-2023-september-2023). Please use monitor downtime or muting rules instead.Use Monitor Downtimes to stop the execution of synthetic monitors.
Use Muting Rules to prevent notifications from being sent from alert conditions that include synthetic monitors.