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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Mark an alert as significant

# Mark an alert as significant {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Make an alert more likely to be included in a Log Analytics group when
the associated metric behaves anomalously by labeling the alert as meaningful.

## Before you begin

Role required: evt_mgmt_operator or evt_mgmt_admin

## Procedure

1. In the Service Operations Workspace, open a Log Analytics alert and then select Apply ML feedbackMark as significant.
2. Confirm the action in the dialog box.  
   Note:  
   Processing this feedback might take a few seconds.
3. **Optional:** Restore the significant alert.  
   If you no longer want the significant alert to be treated specially, you can restore normal significance to the alert metric. For more information, see [Restore normal importance to an alert metric](https://www.servicenow.com/docs/x6HOHEw2QkvI5KJaPbp9QQ "Return normal significance to the metric involved in generating a Log Analytics alert. Use this option if you no longer want an alert to be treated specially that was muted, marked as significant, or made less sensitive to similar anomalies.").
{#hla-op-alert-make-significant-sow__steps_px5_z51_gtb}

*[\>]: and then