Notification Rules

What are Notification Rules?
With notification rules, you can perform custom notification sequences. Notification rules are processed after PagerTree has selected the account user to notify, but before default notification channels are used. The diagram below shows the high level workflow for alerts and how they move within the PagerTree system.
Notification rules are objects that can dynamically change a notification cycle.
Notification rules only apply to the Alert open message.
Notification rules must be attached to an account user to be used.
To access notification rules, you must enable "advanced mode".
Notification rules are evaluated in top down order.
If no rules are matched, the account user is notified on their default notification channels.
Notification rules are written in YAML.
High Level Alert Workflow (Notification Rules)
Notification Rules Video
Notification Rules Tutorial Video (v4)
Rules Syntax
The notification rules syntax is the same as routers.
The match block works exactly the same (data and operators are the same)
The actions block works exactly the same but with different actions.
Please see the routers documentation for rules syntax and match conditions.
Remember to come back here for notification rule specific action types.
Actions Block
Action Types
​notify - Notify the user on specific channels.
​repeat - Repeat the notification cycle.
​ignore - Suppress notifications from being sent.
Notify
The notify action will notify the account user on specified channels then wait for a timeout for next instructions.
Parameters
channels - array - any of the following: push, email, sms, voice, slack
timeout - string - ms notation of the duration to wait before the next action.
- type: notify
  channels:
  - email
  - slack
  timeout: 1m
Repeat
The repeat action will repeat the above notify actions n times. You can repeat between 0 and 3 times.
Parameters
times - integer - the number of times to repeat the notification cycle.
- type: repeat
  times: 1
Ignore
The ignore action will suppress sending any notifications to the account user when matched.
- type: ignore
Putting It All Together
Attach the Notification Rules to your User
When you are happy with your notification rule definition you must connect the Notification Rules to the User.
1.Navigate to the My Settings Page.
2.Scroll to the Other Settings section.
3.Select the notification rule definition from the Notification Rules select box. 
Select the notification rule.
4.Click Update.
Examples
Example #1 Match Everything
Matches everything
1.Notify email, sms, slack (wait 1 minute)
2.Notify voice (wait 5 minutes)
3.Repeat the above cycle 1 more time
# Notify me via email, sms, & slack. 
# If the alert is still open after 1 minute, notify me via voice. 
# If the alert is still open 5 minutes later, repeat this cycle.
---
rules:
  - match:
      always: true
    actions:
    - type: notify
      channels:
      - email
      - sms
      - slack
      timeout: 1m
    - type: notify
      channels:
      - voice
      timeout: 5m
    - type: repeat
      times: 1
Example #2 Special Alerts and Working Hours
Match alerts with title containing "special title" (case insensitive)
1.Notify email, sms, slack (wait 1 minute)
2.Notify voice (wait 5 minutes)
3.Repeat the above cycle 1 more time
Match medium or low urgency alert outside of working hours
1.Ignore
Else, notify via default notification channels.
# match alerts with the title containing "special title" (case insensitive)
  # Notify me via email, sms, & slack. 
  # If the alert is still open after 1 minute, notify me via voice. 
  # If the alert is still open 5 minutes later, repeat this cycle.
# match alerts with urgency medium or low, and outside of working hours
  # do not notify me
# if none of the above match, notify my default channels (not written, implied)
---
rules:
  - match:
      alert.title:
        "$regex": "special title"
        "$options": "i"
    actions:
    - type: notify
      channels:
      - email
      - slack
      timeout: 1m
    - type: notify
      channels:
      - voice
      timeout: 5m
    - type: repeat
      times: 1
​
  # if the alert urgency is medium or low, and outside of working hours do not notify me
  - match:
      $and:
        - alert.urgency:
            "$in":
            - low
            - medium
        - $timeBetween:
            timeformat: 'hh:mm a'
            timezone: 'America/Los_Angeles'
            starttime: '05:00 pm'
            endtime: '08:00 am'
    actions:
    - type: ignore
Common Mistakes
Forgot to Attach to User
Many times a customer has written the notification rule correctly but forgets to attach the notification rule to the user.
Don't forget to attach the notification rule to the user!
Bad Indentation
A common error when configuring notification rules is that the YAML is not formatted correctly (mostly always indentation). You can use the JSON2YAML tool to check your indentation.
FAQs
Question
Answer
What happens if the escalation layer timeout is shorter than my entire notification rule cycle?
The notification rule cycle will stop after the escalation layer times out. It's possible that all notify actions are not reached because the escalation layer timing out.
Broadcasts don't seem to be respecting my notification rules, why?
Notification rules are only applicable when being notified about an Alert.

Question	Answer
What happens if the escalation layer timeout is shorter than my entire notification rule cycle?	The notification rule cycle will stop after the escalation layer times out. It's possible that all notify actions are not reached because the escalation layer timing out.
Broadcasts don't seem to be respecting my notification rules, why?	Notification rules are only applicable when being notified about an Alert.

Routers

Single Sign On (SSO)

Last modified 4mo ago