Incident grouping is useful in preventing multiple alerts about the same incident. When incident grouping is set up, incidents that are likely related will be grouped together.

Configuring the sensitivity of incident grouping

• Go to Settings → Teams.
• Click ⋯ next to the team you want to configure incident grouping for and select Features.
• Under Incident grouping, select the timeframe in the Group incidents dropdown. For example, Triggered within 3 minutes.
• Click Save changes.

Keeping unrelated incidents apart

Under Don't group together incidents if the following combination of metadata is different, add metadata keys that must match for incidents to be grouped together. For example, add environment to keep staging and production incidents in separate groups.

Grouping incidents from different sources

Better Stack adds an Origin metadata key to every incident naming where it came from, such as Monitor, Datadog integration, or Incident form. Origin starts in the field above, so incidents from different sources stay in separate groups.

Remove Origin to group incidents from every source together, for example to collect alerts from several integrations into one group. Monitors, heartbeats, integrations, and manually reported incidents are then grouped whenever they start within the timeframe you selected.

Notifications for grouped incidents

By default, you are notified about every incident in a group. Turn off Notify about all incidents in a group to be notified only about the first incident in a group.

Turning this off can hide critical incidents

A minor incident that arrives first becomes the group's only notification, so a critical incident grouped with it stays silent. Keep different severities in separate groups by adding Escalation policy or other metadata keys to the grouping scope. If you removed Origin, this applies across every source, so an alert from one integration can silence an incident from another.