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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Assigning higher or lower significance to an alert

# Assigning higher or lower significance to an alert in Health Log Analytics {#ariaid-title1}

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

Label an alert as meaningful or insignificant, or restore normal importance to the metric involved in generating it.
* **[Mark an alert as significant in Health Log Analytics](https://www.servicenow.com/docs/e93FRLSwkAzsy9mgaRnsRQ)**   
  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.
* **[Mute an unimportant alert in Health Log Analytics](https://www.servicenow.com/docs/hUPCkZ4mOr3MvTtGHRX1Sw)**   
  Eliminate distracting new alerts for insignificant issues by muting them.
* **[Decrease sensitivity to similar anomalies in Health Log Analytics](https://www.servicenow.com/docs/j_Af9oWQAFgdBd1OC~jqKQ)**   
  Make anomaly detection less sensitive to anomalies like the one that triggered the current Log Analytics alert.
* **[Restore normal importance to an alert metric in Health Log Analytics](https://www.servicenow.com/docs/k~cHFXUx6~usMDuJ_il94w)**   
  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.