Trigger Flood Control

In xMatters, triggers capture data from incoming signals and use this information to run flows that prevent and resolve service availability issues. Trigger flood control inspects the signals targeting a trigger and prevents correlated signals that occur in quick succession from triggering the flow. This reduces system noise and duplication of activities for the same issue.

Once flood control kicks in, it continues to suppress signals from triggering a flow until the rate of correlated signals drops below the rate specified in the trigger conditions (by default, four or fewer signals per minute). When the flood is over, xMatters resumes allowing signals to trigger the flow.

You can view information about signals coming into xMatters, including suppressed signals, in the Signals report.

Manage trigger flood control settings

The Trigger Flood Control page in the web user interface allows you to view and manage flood control settings for each trigger.

Required permissions

To manage flood control settings for a trigger, you'll need the following:

Configure flood control for a trigger

This section describes how to configure flood control for HTTP, Email, App, and Form triggers.

View suppressed signals

If signals exceed a trigger's flood control conditions and correlation rules, xMatters suppresses them from triggering the flow. You can view suppressed signals in the Signals report. Signals are suppressed beneath the most recently processed signal to which they correlate (the "parent" signal). This is indicated on the Signals report by a stacked icon with a running badge count of the number of suppressed signals.

To view more information about suppressed signals, click the stacked icon beneath the parent signal.