---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Tag cluster alert grouping

# Tag cluster alert grouping {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Tag cluster alert grouping enables you to easily create groups of alerts. It is a non-code method of alert grouping that correlates alerts without having to use CMDB or model training. This simpler way of grouping similar
alerts reduces the overall noise of a large quantity of alerts.  
Note:  
To group alerts using tag-based grouping, create a grouping automation in Service Operations Workspace. For more information, see [Create Group automation](https://www.servicenow.com/docs/OM3oKI7Rry_Wahava5K1Kw "Grouping automation helps you manage alerts more effectively by collecting similar alerts together. This makes it easier to see patterns, quickly identify issues, and respond efficiently. By organizing alerts in this way, you can reduce alert noise, identify root causes, and assign them to the appropriate teams.").

Tag cluster alert grouping is enabled immediately after the activation of the Tag-Based Alert Clustering Engine application, available in the ServiceNow Store. This grouping is applied according to the correlation logic order specified in the [Configure alert correlation logic order](https://www.servicenow.com/docs/~c2xwOB1O9ne_ZBazLUxNw "Improve alert management by enabling users to customize correlation logic order. This feature empowers you to fine-tune correlation methods to their specific needs, enhancing alert prioritization and response efficiency."). Alert grouping tags are attached to definitions on a many-to-many (M2M) basis. Multiple tags can be linked to a single definition, and a tag can be part of multiple
definitions. Groups formed from tag cluster alert grouping definitions are classified as the Tag Cluster group type.

Tag cluster alert grouping supports domain separation, allowing different domains to have their own distinct alert grouping configurations and logic.

First, create alert grouping tags to define the criteria for grouping alerts. You can set the tags to require an exact match, an approximate ('fuzzy') match, or a character pattern match.

Preconfigured tags are also available to speed up alert clustering. These tags are mapped from alert fields, alert tags, or alert additional info. If the required data is missing and the tag source is Alert CI or Alert CI key, the
tag uses the Configuration Item (CI) value from the Configuration Management Database (CMDB). Preconfigured tags include "out of the box" in their description.

You can attach one or more tags to an alert clustering definition, which specifies the conditions for alert correlation. You can either create your own alert clustering definition or use a predefined one provided by the
application. Predefined definitions come with associated tags.  
Important:  
Make sure to activate predefined definitions before use. In new systems, several definitions are active by default. The remaining ones must be activated. For more information, see [Activate a predefined alert clustering definition](https://www.servicenow.com/docs/WOjkIIDYgZ6RAFxZdOxelg "Activate the predefined alert clustering definitions provided with the Tag-Based Alert Clustering Engine application before use. Utilizing these preconfigured definitions minimizes setup time and ensures a more efficient configuration process, allowing for quicker implementation and streamlined alert management.").

After tags are attached to a definition, alerts with matching or similar tag values are grouped together. New alerts join an existing group if their tags match those in the definition.

For tag-cluster grouping, alerts are added to a group based on the timeframe defined in the alert clustering settings. The time between the initial alert (virtual alert) and subsequent alerts is evaluated. If two new alerts are
received, and their time difference falls within the defined timeframe, they are added to the group. The initial event's generation time is used to determine the relevance of the timeframe.
**Related concepts**   

* [Alert tags](https://www.servicenow.com/docs/LSntrpYNm1zxh5joyf89WQ "Alert tags consolidate normalized alert fields (key/value) across sources, improving alert quality for correlation and expanding out-of-the-box TBAC (Tag Based Automatic Correlation) definitions.")  
**Related tasks**   

* [Create alert clustering tags](https://www.servicenow.com/docs/oxNcdpa7XcZT22z5OmXkvg "Create streamlined alert correlations with alert clustering tags by grouping alerts that share identical or similar tags based on your configured match method. This reduces noise, enhances incident prioritization, and improves operational efficiency, enabling faster issue resolution and response times.")
* [Create an alert clustering definition](https://www.servicenow.com/docs/8aTh_pBR63fQTOemyZ46OQ "Define alert clustering conditions to trigger one or more alert clustering tags, which help create alert groups from fewer alerts. Creating alert groups from fewer alerts reduces noise, making it easier to identify critical incidents, prioritize responses, and manage issues effectively.")
* [Activate a predefined alert clustering definition](https://www.servicenow.com/docs/WOjkIIDYgZ6RAFxZdOxelg "Activate the predefined alert clustering definitions provided with the Tag-Based Alert Clustering Engine application before use. Utilizing these preconfigured definitions minimizes setup time and ensures a more efficient configuration process, allowing for quicker implementation and streamlined alert management.")
* [Attach a predefined tag to an alert grouping definition](https://www.servicenow.com/docs/nxgnRvZ87IF4mOXyirfNeQ "Get started faster with alert clustering by attaching a predefined alert clustering tag to a tag-based alert clustering definition in Event Management. By associating a predefined tag, you ensure that alerts meeting the specified criteria are grouped effectively, facilitating quicker identification and response to related incidents.")
* [Configure an event rule to customize alert content](https://www.servicenow.com/docs/tnTSXhl5Zinn8JuUTjkkIg "You can configure an event rule to customize alert content. You can customize the order of the fields and select which fields display. The fields in the left-hand work area of the Transform and Compose Alert Output section of an event rule are the fields that appear in the generated alert.")

