Alert rule templates

Use templates to set up common alert rules to deal with incidents based on priority and severity.

Spike.sh - Alert rule templates

Let's look at some of the examples

IF

Incident has occurred at least 5 times within last 10 minutes

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

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 Easiest Way to Manage Incidents and get Ahead of Service Degradation and Disruptions

Get started

Risk free 14 days trial
No credit card required

Discover more

Incident Management

Alerting

Collaboration

Comments
& Notes

Monitoring