Event Flood Control

During an event flood, the first events to arrive typically contain the details you need to identify which of your systems need attention. Subsequent events that are generated during a flood add a lot of extra noise and they can result in processing delays if you exceed your licensed number of events per minute.

Event flood control reduces the number of events that are generated in xMatters when you experience a flood or event storm from one or more of your systems.

How does it work?

This feature compares incoming event requests to recent events and suppresses correlated events that occur in too close succession to one another. When suppression kicks in, xMatters sends you a notification and logs the details of the flood on the Events report so you can track how many events were suppressed and why. These suppressed events aren't queued for processing and don't count against your licensed number of events per minute, which allows events from other sources to flow through xMatters without lengthy processing delays.

Default Event Rate Filter

As of the Defender release of xMatters On Demand, a default Event Rate Filter applies to all new and existing inbound integrations. The default event rate filter automatically suppresses incoming events from the same integration that target the same recipients when they occur at a rate that exceeds four events per minute.

This default rule is based on our analysis of actual customer event flood data and provides a balance of effective protection against sudden influxes of events, while allowing real traffic to proceed as normal. For more information on how you can enable or disable the default rule for an integration, see Manage Event Flood Control Settings.

Manage Event Flood Control Settings

The Defender release of xMatters On-Demand introduces a new Event Flood Control page in the web user interface, which allows you to view and manage event flood control rules for individual communication plans and built-in integrations.