Alert rule template
Change escalation for P5
If incident priority is P5, change the escalation policy
Use template

IF

Incident has P5 priority

THEN

Change escalation policy to Website uptime policy
All Alert rule templates

IF

Incident has occurred at least 5 times within last 10 minutes
AND
Incident has P1 priority

OR IF

Incident title contains Down

THEN

Mark severity as SEV1
Set High severity
Add all conditions that will change an incident's severity to SEV1 (which is high). You can edit this rule to change the escalation policy too.

IF

Incident has occurred at least 5 times within last 10 minutes

OR IF

Incident has SEV1 severity

OR IF

Incident has P1 priority

OR IF

Incident title contains DOWN

THEN

Change escalation policy to Website down policy
AND
Reassign incident to Adam Smith
Change escalation on Critical incident
Detects if incident is critical based on priority, severity, and checking for keywords in an incident message.

IF

Incident has P5 priority

OR IF

Incident title contains Testing

OR IF

Incident title contains Development

THEN

Do not create incident
Do not create incident
Some incidents are best to be ignored, add all conditions here to avoid creating an incident

IF

Incident has P5 priority

THEN

Change escalation policy to Website uptime policy
Change escalation for P5
If incident priority is P5, change the escalation policy
TRY THE WORLD'S SIMPLEST WAY TO HANDLE INCIDENTS AT JUST $7/MONTH

It takes only 5 minutes to setup your first integration and receive an alert with an example incident.

Get started 
Schedule a demo with us
  • • No credit card required
  • • Risk free 14-day trial
  • • Cancel anytime
TRY THE WORLD'S SIMPLEST WAY TO HANDLE INCIDENTS AT JUST $7/MONTH

It takes only 5 minutes to setup your first integration and receive an alert with an example incident.

Get started 
Schedule a demo with us
  • • No credit card required
  • • Risk free 14-day trial
  • • Cancel anytime
© 2023 FatSync Software Private Limited. All rights reserved