1. Home
  2. Alert Behavior
  3. Notifications
  4. Notification & Alert Aggregation

Notification & Alert Aggregation

Notification Aggregation

Notification aggregation is applied to each notification type (push, sms, email and phone) on a per user basis. This means push notifications going to user A are aggregated separately than SMS for user A. Each time a notification is sent out it is cumulative for the total # of incidents for that user.

The current notification settings are:

  • Push, SMS, Email: 3 events / 60 seconds
  • Phone: 1 event / 2 minutes

Aggregation does not trigger until there are at least 3 incidents opened in a 60 second period. Below is an explanation of a few different scenarios.

Action in Timeline Aggregation Expected Response
Two incidents are created in the Timeline in under 60 seconds x Notifications sent out for both incidents to the user(s) on-call
Four Incidents are created in the Timeline in under 60 seconds Three notifications sent out during the first minute then one in the following minute
Ten Incidents are created in the Timeline every minute for five minutes Three notifications sent out during the first minute and then one for the following 4 minutes

Alert Aggregation

We aggregate alerts based on the entity_id field within the incident payload. Below you will see an Incident that has multiple alerts, because of the same entity_id. If an Incident is in an Ack’d or Triggered state, while multiple alerts with the same entity_id are coming in, we only page out based on the original alert.

notificationalert1

Updated on June 14, 2017

Was this article helpful?

Related Articles