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


---

# Controlling alert generation, prioritization, and anomaly detection

# Controlling Health Log Analytics alert generation, prioritization, and anomaly detection {#ariaid-title1}

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

Influence how Health Log Analytics generates and prioritizes alerts and identifies anomalies. Use alert filters to reduce noise from unimportant issues.

## Overview of impacting alert generation, prioritization, and anomaly detection {#hla-controlling-alert-generation__cf-using-parent-workflow}

Explore how to influence alert generation and anomaly detection in Health Log Analytics. You can create and modify rules to generate alerts for specific metrics, ensuring that you are informed of important issues. You can also assign different levels of significance to alerts,
helping Health Log Analytics prioritize them based on their relevance. In addition, you can influence anomaly detection by managing the keywords that Health Log Analytics looks for in your log data, and use advanced log alert filters to reduce noise.

* [Use alert rules to control when Health Log Analytics generates alerts](https://servicenow-prod.fluidtopics.net/XtlZr0V6VIMgumgHBXIA3Q "Alert rules enable you to set thresholds and conditions that determine when Health Log Analytics triggers an alert. When the conditions of an alert rule are met, the system generates a Log Analytics alert. You can add, change, or delete alert rules to create Log Analytics alerts for a specified metric.")

  Manage alert rules to generate Log Analytics alerts for specified metrics.
* [Assign higher or lower significance to an alert in Health Log Analytics](https://servicenow-prod.fluidtopics.net/GWEhrWJ5Dz7Z8kZm84yw3A "Label an alert in Health Log Analytics as meaningful or insignificant, or restore normal importance to the metric involved in generating it.")

  Assign higher or lower significance to an alert to help prioritize the alerts that Health Log Analytics generates.
* [Influence anomaly detection in Health Log Analytics with lexical keywords](https://servicenow-prod.fluidtopics.net/E~BJE_mSsw4k6AFCNexMag "Influence how Health Log Analytics finds anomalies by managing keywords it looks for in your log data. When text in log data for a source matches a lexical keyword that exceeds a specified count threshold, the system identifies an anomaly and generates an alert.")

  Influence how Health Log Analytics finds anomalies by managing keywords it looks for in your log data.
* [Reducing noise by adding advanced log alert filters in Health Log Analytics](https://servicenow-prod.fluidtopics.net/zokVf2Sqn8uEzozJyuptRw "Use advanced log alert filters to determine whether to allow an alert or to drop it. These filters reduce noise by dropping alerts that don't indicate a significant issue.")

  Use advanced log alert filters to reduce noise by making Health Log Analytics drop alerts that don't indicate a significant issue.
{#hla-controlling-alert-generation__cf-using-parent-steps-ul}