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

# Assigning higher or lower significance to an alert {#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 in Health Log Analytics as meaningful or insignificant, or restore normal importance to the metric involved in generating it.
Assigning higher or lower significance to an alert helps you prioritize the alerts Health Log Analytics generates. Here are some common use cases for adjusting the importance of an alert:

* Labeling alerts as meaningful: You can make a significant alert more likely to be included in a Log Analytics group when its associated metric behaves anomalously. This ensures that important alerts receive appropriate attention.
* Muting distracting alerts: You can mute alerts for insignificant issues to reduce noise and avoid being overwhelmed by alerts for minor problems. This enables you to focus on more critical alerts. You can view a list of muted metrics to ensure you are aware of metrics that are no longer generating alerts.
* Reducing sensitivity to certain anomalies: You can lower the sensitivity of anomaly detection to a specific anomaly. This can help you focus on more significant anomalies.
* Restoring normal significance: If you previously marked an alert as significant, muted it, or if you lowered sensitivity to certain anomalies, you can return the associated metric to its normal significance. This is useful when you no longer want to treat the alert specially.
{#hla-op-alert-significance__ul_rgn_wpt_22c}  
You can do the following to adjust the importance of an alert or reduce sensitivity to specific anomalies:

* [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.")

  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.")

  Eliminate distracting new alerts for insignificant issues by muting them. [View the list of metrics that were muted](https://servicenow-prod.fluidtopics.net/MwQ5spiRfc5M9~G6475pTQ "View the list of metrics that were muted so that they no longer generate alerts.") and no longer generate alerts.
* [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.")

  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.")

  Return normal significance to the metric involved in generating a Log Analytics alert.
{#hla-op-alert-significance__ul_fp3_mp2_32c}

For detailed information about alert metrics, see [How Health Log Analytics generates alerts](https://servicenow-prod.fluidtopics.net/zaqeZmmJdcaBNEqfu4~1Ww "Health Log Analytics identifies patterns in your log data and learns pattern behavior. When HLA's AI engine detects anomalous behavior, it sends an event to the ServiceNow Event Management application. As an operator, you can use these predictive alerts to handle emerging IT issues before they impact users.").
* **[Mark an alert as significant](https://servicenow-prod.fluidtopics.net/vbBe7V4SM7Jxz9B0cubT7A)**   
  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/ognPpLajLU0OZ4bNrWuNAw)**   
  Eliminate distracting new alerts for insignificant issues by muting them.
* **[Restore a muted alert or a significant alert](https://servicenow-prod.fluidtopics.net/ZapYmJxNos59Ukxgg~ZLLw)**   
  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.