1. Overview

Ping suppression is a mechanism that helps manage the creation of pings (alerts) when an entity triggers a rule, e.g. defined threshold. This prevents excessive duplicate pings and ensures that users can focus on actionable cases without unnecessary noise.

2. How Ping Suppression Works

1. Initial Ping Creation:

   • A ping is generated when an entity surpasses a predefined criteria in rule, e.g. transaction threshold.

2. Ongoing Suppression for Pending Pings:

   • No new pings will be created while the existing ping remains in a "pending" state, as long as the entity does not exceed the threshold parameters again.
   • This prevents multiple pings for the same event until an action is taken.

3. New Ping Creation After User Action:

   • If the existing ping is acted upon (marked as "confirmed," "resolved," or "ignored"), a new ping will be generated when the threshold is reached again.
   • This ensures that once a case is reviewed, future violations of the threshold can still trigger alerts.

4. Muted Rules and Complete Suppression:

   • If pings are muted for a specific rule, no pings will be generated at all, even if an entity reaches the threshold.
   • Muting is useful when temporarily suspending pings for specific rules or testing configurations.

3. Example Scenario

Rule: Monitoring incoming transaction volume over a rolling 10-day period, with a threshold of 1,000 SEK.

Case 1: Suppression While Pending

• On Day 3, an entity accumulates 1,000 SEK in transactions → Ping is created.
• The ping remains in pending status.
• Over the next few days, additional transactions occur, but as long as the entity does not exceed the threshold parameters again, no new pings will be triggered.

Case 2: New Ping After Exceeding Again

• On Day 7, the entity reaches 1,000 SEK again within the rolling 10-day period.
• Since the threshold is exceeded again within the timeframe, a new ping is created.

Case 3: New Ping After Action is Taken

• If the first ping is confirmed, resolved, or ignored, the next time the entity reaches 1,000 SEK within a 10-day rolling window, a new ping will be generated.

Case 4: Muted Rule - No Pings Created

• If muting is enabled for this rule, no pings will be created at all during the muting period, even if the entity surpasses the threshold multiple times.

By using ping suppression effectively, users can reduce redundant notifications while maintaining a strong monitoring process for high-risk activities.