Return to list

Alerts | {{heading}}

Condition
Based on
The metric that this alert monitors.
The transaction type that this alert monitors.
(Optional) The transaction name that this alert monitors.
The transaction response time percentile to use for alerting.
(Optional) Count errors that contain this text in the error message. The comparison is case-sensitive. Enclose the text in forward slashes to use a regular expression, e.g. /Read timed out|Connection reset/ will count errors that contains either "Read timed out" or "Connection reset" in the error message.
{{unit}}
This is required.
This is invalid.
If the {{phraseForValue()}} over the given time period is greater than or equal to this threshold, then alert will be triggered.
Alert if the {{phraseForValue()}} is less than or equal to the threshold, instead of alerting if the {{phraseForValue()}} is greater than or equal to the threshold.
The time period over which the {{phraseForValue()}} is calculated.
Time periods with very few transactions have much less meaningful metrics, so this can be used to suppress alerts from being generated unless the time period has a minimum transaction count.
The time period after which the alert is triggered if no heartbeat has been received from the agent. Heartbeats are normally received every 5 seconds.
The synthetic monitor that this alert is based on.
If the synthetic monitor duration is greater than or equal to this, then it is considered a failure.
If the synthetic monitor fails this number of times in a row (by either exceeding the duration threshold or returning an error), then the alert will be triggered.
Severity
Email notification
Comma separated list of email addresses.
PagerDuty notification
Slack notification
Comma separated list of channels, e.g. #alerts