---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Exclude patterns from learned patterns

# Exclude patterns from learned patterns {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Exclude CI-based or CI class-based alerts and patterns when you encounter alerts incorrectly added to a learned pattern by the Learned Patterns job. For example, a pattern might include an alert that occurred at the same time
as other alerts but is not actually related to them. This maintains accuracy, ensuring better alert groupings and improved management efficiency.

## Before you begin

Role required: evt_mgmt_admin

## About this task

You select the incorrect alert in a pattern to exclude the entire pattern to which it belongs.  
Note:  
When you exclude an incorrect alert, any other patterns containing that alert are also excluded.

## Procedure

1. Navigate to AllEvent ManagementReportingLearned Patterns.  
2. On the Learned Patterns page, expand the anomalous pattern.  
3. Select the pattern name to open it for exclusion.
4. On the SA Alert Aggregation Learned Pattern page, select Exclude.  

## Result

The entire pattern is removed from the Learned Patterns report and listed on the Excluded Patterns page, located at Event ManagementAdministrationExcluded patterns.

If the pattern includes other alerts, you can restore it by reclaiming those alerts as a learned pattern. For further details, see [Restore excluded patterns](https://servicenow-prod.fluidtopics.net/Z3SADu8iJuJ8axM6qf0q5w "Restoring excluded patterns to the learned patterns report lets you reintegrate valuable insights lost due to incorrect alerts. This flexibility maintains accurate alert aggregation and enhances monitoring. For example, if you excluded a pattern due to an incorrect alert, you can restore it without that alert, ensuring relevant data remains accessible for analysis and decision-making.").

*[\>]: and then