Why noise reduction
Core concepts
Before understanding noise reduction, you need to understand the relationship between three core objects:- One alert can contain multiple events (events with the same
alert_keythat arrive within the Event Aggregation window, plus the corresponding recovery events) - One incident can contain multiple alerts (similar alerts grouped together)
- Noise reduction happens at two stages: Event Aggregation controls “Event → Alert”; Alert Grouping controls “Alert → Incident”
Noise reduction process
When a monitoring system pushes alerts to Flashduty On-call, the system automatically executes the following workflow:Receive Event
Process New Alert
Trigger Notification
Subsequent Alerts Merge

Let AI configure noise reduction for you
The header of the Alert grouping and Flapping detection pages carries a Let AI tune noise reduction button on the right. It opens AI SRE in the side panel, takes this channel along as a context reference, and prefills a request for the page you are on:/channel-noise is the matching built-in Skill, reachable only from this entry, and it tunes one channel per session. You can send the prefilled request as it is, or rewrite it first, for example to narrow the look-back window or to name the grouping dimensions you must keep. After that you keep talking in plain language to refine what you asked for.
labels.check → labels.check + labels.service”) and only your confirmation writes it. The change takes effect immediately.
/channel-noise changes Alert grouping and Flapping detection only. For Event aggregation, silence rules, inhibit rules and drop rules it recommends what to change and names the page to change it on, but never writes. For how a reference tag travels with a message and how sessions are managed, see Console chat.
Event aggregation
Go to Channel Details → Configuration → Noise Reduction → Event Aggregation to configure. Event Aggregation controls the “Event → Alert” merge. When the monitoring system keeps pushing events with the samealert_key, it decides whether they merge into the existing alert or each create a new one.
An event merges into an existing alert only when all four conditions hold. If any one of them fails, Flashduty creates a new alert:
- Same channel: the event and the target alert belong to the same channel
- Same
alert_key: the event describes the same alert lifecycle - Target alert still active: recovered or ended alerts no longer accept events
- Still inside the aggregation window: after the window expires, a matching
alert_keystill creates a new alert
Configuration
Versus alert grouping
Alert grouping
Go to Channel Details → Configuration → Noise Reduction → Alert Grouping to configure. Alert grouping merges multiple similar alerts into a single incident for unified assignment and notification. When an alert storm hits, you only need to handle one incident instead of hundreds of repeated notifications.labels.check), and Pro and on-premises deployments to Intelligent grouping (default fields for the similarity judgement: title, description, labels.service, labels.resource). With these defaults the aggregation window is until the incident closes, alert storm warning is off (default threshold 100 once enabled), and strict grouping is off. You can pick another available method in the wizard, or change it later under Noise Reduction → Alert Grouping. For the wizard step, see Create a channel.Grouping modes
The Alert Grouping page offers three mutually exclusive methods. A choice takes effect only after you save it:group_method carries the same choice: i (intelligent grouping), p (rule-based grouping), n (no grouping); see Incident webhook.
Clicking another method card shows that method’s settings right below, with no confirmation dialog, and any draft you filled in before switching is kept. Nothing takes effect until you click Save.
Common configuration
- Intelligent Grouping
- Rule-based Grouping
- No Grouping
Select Grouping Mode
Select information used for matching

Intelligent Grouping Configuration
Preview rule grouping
After selecting Rule-based grouping and filling in the configuration, click Preview at the bottom to see how the current draft groups a sample of recent alerts. The result includes event, alert, and incident counts, plus the alerts in each incident. Previewing does not save the configuration. Click Save to apply the rule after reviewing the results.Configuration limits
Grouping configuration has these limits:Grouping effect
After setting grouping by Alert Check Item, Flashduty groups 5 events into 3 alerts, and the 3 alerts into 1 incident:- Click alert title to view alert timeline and associated events
- Click event point to view specific event content

Grouping Effect Display
Flapping detection
When the same incident triggers and recovers frequently, the system marks it as “flapping” status to avoid notification bombardment. Go to Channel Details → Configuration → Noise Reduction → Flapping Detection:
Configurable parameters
Silence rules
During maintenance windows or known issue periods, silence rules can suppress alert notifications for specific conditions. Go to Channel Details → Configuration → Noise Reduction → Silence Rules. The Search name or description box above the list filters it by rule name and description, case-insensitively. It does not match the values inside the conditions, and the list shows No matching results when nothing matches.Silence time
1d) plus an absolute time-range picker on the right. The two controls stay in sync:
- Duration accepts shorthand such as
30m,1h,12h,1d,1w,2w. Changing the duration recomputes the end time from the current moment. - You can also pick the start and end directly on the right; the duration input updates accordingly.
- Start time must be earlier than end time, and neither field may be empty.
Silence conditions
Define which alerts to silence. You can combine multiple conditions.- AND: All conditions must be met to silence
- OR: Any condition met triggers silence
Silence behavior
Quick silence
Quickly create temporary silence rules based on existing incidents. Operation Path: Incident Details → More Actions → Quick Silence- Rule name defaults to “Quick Silence - #short-ID”, with the incident title included in the description
- Effective scope is the incident’s channel (cannot be changed)
- One-time silence is the default and lasts 1 day. Type a custom duration on the left (such as
30m,1h,12h,1d,1w, or2w), or pick an absolute time range on the right. Flashduty deletes a one-time rule after it expires - You can instead select recurring silence and configure the silenced time windows with the standard recurring schedule
- Conditions default to severity plus filtered labels. Flashduty excludes two kinds of labels. System format rules exclude label values that are JSON, numeric, datetime-formatted, or overly long. Account exclusion rules exclude labels globally or per integration (see Quick-silence label exclusion rules)

Quick Silence Configuration
Copy a silence rule
Silence rules are listed in a table; click a row to expand it and see the rule’s details. In that list, open More actions (⋯) on the target rule and choose Copy (not offered for rules created by Quick Silence) to set the new rule’s name, description and target channel:Inhibit rules
When a root cause alert exists, automatically inhibit related secondary alerts. For example: When a Critical level incident exists, inhibit Warning/Info level incidents for the same check item.Configuration path
Inhibit conditions
Flashduty inhibits a new alert when all of these hold:- The new alert meets the conditions.
- A matching active alert exists from the last 10 minutes. Any active, unrecovered alert can be the source, acknowledged or not.
- Both alerts share the equal items.
Inhibit behavior
Configuration example
Scenario: When Critical level alerts exist, inhibit Warning/Info level alerts for the same check item.FAQ
Will the incident title change when new alerts merge in?
Will the incident title change when new alerts merge in?
Will incident labels change when new alerts merge in?
Will incident labels change when new alerts merge in?
- Manually created incidents: No, labels list always remains empty
- Auto-triggered incidents: Possibly, incident labels stay consistent with the first alert; if that alert’s labels change, incident labels update accordingly
Will alert labels change when new events merge in?
Will alert labels change when new events merge in?
What's the maximum number of alerts a single incident can group?
What's the maximum number of alerts a single incident can group?
What's the maximum number of events a single alert can be associated with?
What's the maximum number of events a single alert can be associated with?
- Event Aggregation enabled: events with the same
alert_keymerge into the same alert within the window; events arriving after the window expires create a new alert - Event Aggregation disabled: every event creates an independent alert, with no merging
