Notification Flood Control
The notification flood control setting prevents users from being flooded with multiple notifications from an integration when they’ve been notified about an incident and might be already working on resolving the issue from their mobile device.
If notification flood control is enabled for an integration, and that integration generates two or more notifications for voice, SMS, or mobile app devices in a five-minute period, xMatters delivers the first notification to users on their preferred devices. xMatters then suppresses any additional notifications that the integration generates for the same device type. Email notifications and messages sent to the xMatters Inbox are not affected, and will still be delivered.
For example, imagine an incident occurs, and triggers an integration to notify you on your mobile phone. Meanwhile, the incident causes something of a chain reaction in your system, causing multiple incidents to occur, all triggering the same integration. If you enabled notification flood control on that integration, xMatters will suppress additional notifications from that integration to your voice devices for the next five minutes. You’ll be able to see the events and follow the trail of notifications in your xMatters Inbox and reports, and you won’t have to stop working on your solution to answer your phone every few seconds.
When enabled for an integration, notification flood control applies to notifications that target users directly, via subscriptions, or through activity updates. If a user previously received a notification from an integration by any of these methods, any additional notifications to the same device type for that user during a 5-minute period by any of these methods are suppressed.
Notification flood control also overrides the 'Allow Duplicates' setting for groups. Only one notification is sent to the same device type of a particular user when that user is in more than one group and they would have been notified more than once in a five-minute period. (If xMatters fails to deliver a notification, it will automatically try again; retries are not suppressed, even if they would otherwise be subject to notification flood control.)
The Events report and Log audit report indicate events where notifications were suppressed. See Events Report for more information.
Enable notification flood control
Notification flood control is disabled by default. This setting can be enabled for inbound integrations that use the form.post method to trigger a form. This includes 'Create a new xMatters event' and 'Transform content to create a new xMatters event' inbound integrations.
Notification suppression does not apply to inbound integrations that use HTTP POST to call a form from inside an Integration Builder script.
To enable notification flood control for an inbound integration:
- On the Integration Builder tab, expand the list of inbound integrations.
- From the Settings drop-down list (the gear icon) beside an integration, select or clear the check box for Flood Control.
Notification flood control is also available for built-in integrations in the Integration Directory. For more information, see Enable notification flood control for a built-in integration.