---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Mute an unimportant alert

# Mute an unimportant alert in Health Log Analytics {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Eliminate distracting new alerts for insignificant issues by muting them.

## Vorbereitungen

Role required: evt_mgmt_operator or evt_mgmt_admin  
Wichtig:  
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: [Mute an unimportant alert in Health Log Analytics](https://servicenow-prod.fluidtopics.net/OKk4bgWDloVT3TzqCBX9wQ "Eliminate distracting new alerts for insignificant issues by muting them.").

## Warum und wann dieser Vorgang ausgeführt wird

When you mute an alert that is based on the keyword metric or the pattern severity metric, the system mutes the metric in the dominant pattern. The dominant pattern is the main pattern that contributes to the anomaly. For the specified source only, anomalous behavior for the metric that is associated with the muted alert no longer generates alerts. You can also mute the metric that is associated with an unimportant alert for all components of the Service instance. A component can be multiple CIs that perform the same function.

## Prozedur

1. In the Service Operations Workspace, open the alert that you don't want to see again.
2. Select Apply ML feedbackMute an alert.
3. Select Apply ML feedback
4. Mute the metric associated with the alert by doing one of the following:
   * Select Mute alert metric to mute the metric for the specified source only.
   * Select Mute alert metric for all components to mute the metric for all components of the service instance.
   {#hla-op-alert-mute__choices_x3y_g4g_vwb}
5. Confirm the action in the dialog box.  
   Hinweis:  
   Processing this feedback might take a few seconds.
6. **Wahlweise:** Restore the muted alert.  
   If you no longer want the muted alert to be treated specially, you can restore normal significance to the metric involved in generating it. For more information, see [Restore normal importance to an alert metric in Health Log Analytics](https://servicenow-prod.fluidtopics.net/F6LzLH~Ec3h9QADJ2LLOEA "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.").
* **[View the list of muted metrics in Health Log Analytics](https://servicenow-prod.fluidtopics.net/COh~dq3VwiAvbK0e~NeqjA)**   
  View the list of metrics that were muted so that they no longer generate alerts.

**Zugehörige Tasks**   

* [View the list of muted metrics in Health Log Analytics](https://servicenow-prod.fluidtopics.net/COh~dq3VwiAvbK0e~NeqjA "View the list of metrics that were muted so that they no longer generate alerts.")