---
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


---

# Restore a muted alert or a significant alert

# Restore a muted alert or a significant alert {#ariaid-title1}

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

If you no longer want a muted alert or an alert that was marked as significant to be
treated specially, you can restore normal importance to the metric involved in generating
it.

## Before you begin

Role required: evt_mgmt_operator or evt_mgmt_admin  
Important:  
From the Vancouver release onward, the Operator Workspace is deprecated and replaced with Service Operations Workspace. For the new procedure, see the corresponding topic in the Service Operations Workspace for ITOM documentation: [Restore normal importance to an alert metric](https://servicenow-prod.fluidtopics.net/gzplutDag2tRcZUlpkbLSQ "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.").