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


---

# Assigning higher or lower significance to an alert in Health Log Analytics

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

* Release version: Yokohama
* 
* Updated January 30, 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](https://servicenow-prod.fluidtopics.net/Z8MDFSA_~ytlkcVf_dMdtg)**   
  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](https://servicenow-prod.fluidtopics.net/r08bZujky4K1GIgi~hFk2w)**   
  Eliminate distracting new alerts for insignificant issues by muting them.
* **[Decrease sensitivity to similar anomalies](https://servicenow-prod.fluidtopics.net/hLrZudo7di~Cm_oY771_Tw)**   
  Make Health Log Analytics anomaly detection less sensitive to anomalies like the one that triggered the current Log Analytics alert.
* **[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.