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


---

# Log Analytics alert rules

# Alert rules in Health Log Analytics {#ariaid-title1}

* Release version: Zurich
* 
* Updated March 15, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Alert rules in Health Log Analytics

Health Log Analytics (HLA) automatically detects anomalies in log data using machine learning based on log patterns.
However, certain log types---especially those with low frequency or critical conditions---may require custom alert rules to ensure reliable detection and alerting.
Custom alert rules allow you to specify metrics, thresholds, and alert properties tailored to your specific monitoring needs.
Show full answer Show less  

## Log Pattern Classification and Detection Logic

HLA categorizes incoming logs into three patterns to determine the appropriate anomaly detection method:

* **Lively:** Logs arrive frequently and consistently (at least once every 20 seconds). Standard anomaly scoring is applied due to sufficient data volume.
* **Sparse:** Logs arrive infrequently or irregularly (less than once every 60 seconds). Probability distribution analysis is used since standard anomaly scoring may be unreliable. Alerts might not trigger if volume is too low.
* **Stopped:** Logs have not arrived for a configured period (default 5 minutes). Configuration options allow tuning the detection thresholds for stopped logs.

## When to Use Custom Alert Rules

* **High-frequency (lively) logs:** Custom rules are optional and only needed to capture specific conditions beyond standard anomaly detection.
* **Low-frequency (sparse) logs:** Custom alert rules are suggested because automatic detection may be unreliable or absent.
* **Known critical conditions:** Custom rules are required to alert on specific log messages or events that may not trigger automated anomaly detection.

## Practical Implications for ServiceNow Customers

By leveraging custom alert rules in HLA, you can enhance alert accuracy and responsiveness for diverse log types across your environment. This enables proactive monitoring of critical services, especially where automated anomaly detection may fall short due to log frequency patterns. Additionally, tuning system properties allows you to customize alert sensitivity for stopped logs according to your operational needs.

## Next Steps

* Define, modify, or delete custom Log Analytics alert rules to tailor alerting behavior.
* Configure HLA system properties to adjust detection parameters for stopped logs.  
Health Log Analytics (HLA) detects anomalies automatically by learning from your log data. However, some log types require a custom alert rule to generate alerts reliably.
You can use custom alert rules to specify the metric, threshold, and alert properties for generating alerts that HLA might not detect automatically.

## Anomaly detection logic by log pattern {#hla-custom-alert-rules__section_mhr_23m_p3c}

HLA classifies incoming logs into three patterns before applying anomaly detection. This classification determines which detection logic is used.
{#hla-custom-alert-rules__table_nbj_4vy_djc__entry__2}

| Pattern | Description |
|-|-|
| Lively | Logs arrive frequently and consistently: at least once in 20 seconds. For example, an application writes hundreds of log entries per hour. The ML Engine has enough volume to build a reliable baseline, so it applies standard anomaly scoring to detect deviations. |
| Sparse | Logs arrive infrequently or irregularly: less than once in 1 minute (60 seconds). For example, a batch job runs every night and writes a small number of log entries. Standard anomaly scoring would produce unreliable results here, so the ML Engine applies probability distribution analysis instead. Sparse logs might not generate alerts if the volume is too low to establish a baseline. |
| Stopped | Logs have not arrived for more than the configured period. Default is 5 minutes (300 seconds). To modify the default value, update the HLA system property `detective.resolution.signal_dead`. For a log stream to be alerted as stopped or dead it must first be considered alive by running continuously for a minimum period of time. You can set this time in the HLA system property `detective.alive_period_seconds_for_signal_dead`. For information about setting and changing HLA system properties, see [Configure global Health Log Analytics system properties](https://www.servicenow.com/docs/0kilMj078sXArYj_WzqNHA "Configure global Health Log Analytics system properties if you need to alter the default values, which should not usually be necessary."). |
[Table 1. Log patterns]

{#hla-custom-alert-rules__table_nbj_4vy_djc}

## When to create custom alert rules {#hla-custom-alert-rules__section_otr_lhm_p3c}

* For high-frequency logs with a lively log pattern, there is no need for a custom rule. However, you can add a rule to generate alerts under specific conditions.
* For low-frequency logs with a sparse log pattern, the system might not generate alerts automatically. If these logs should still generate alerts, define a custom alert rule.
* For known critical conditions that HLA might not flag automatically, define a custom rule. For example, if a specific log message indicates that a critical service has failed, define a rule that generates an alert every time that message appears.

{#hla-custom-alert-rules__ul_xm1_2vy_djc} {#hla-custom-alert-rules__table_cm2_shm_p3c__entry__3}

| Scenario | ML detection | Custom rule |
|-|-|-|
| High-frequency logs with a lively log pattern | Likely sufficient | Optional |
| Low-frequency or periodic logs | Unreliable | Suggested |
| Known critical conditions | Insufficient | Required |
[Table 2. Using custom alert rules]

{#hla-custom-alert-rules__table_cm2_shm_p3c}
**Related tasks**   

* [Define a custom Log Analytics alert rule in Health Log Analytics](https://www.servicenow.com/docs/hC2wwHjV9wI8csVxtrSrhA "Define a custom Log Analytics alert rule for log data that might not generate alerts automatically. A custom rule enables you to specify the metric, threshold, and alert properties directly.")
* [Change a custom Log Analytics alert rule in Health Log Analytics](https://www.servicenow.com/docs/JvlXrM9TcvWKJ5tZrRj7zw "Modify a Log Analytics alert rule that you have defined.")
* [Delete a custom Log Analytics alert rule in Health Log Analytics](https://www.servicenow.com/docs/Jna83Cn~Pbg~IJfFy6hlQA "Delete a Log Analytics alert rule that you have defined if it is no longer necessary.")