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


---

# Overview tab for a Component-based alert

# Overview tab sections for Component-based alerts {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The Overview tab in the Service Operations Workspace helps you understand Component-based
alerts.
For a detailed description of Component-based alerts, see
[Types of Health Log Analytics alerts](https://www.servicenow.com/docs/HukQxEq5jxZUatgCi2wRbg "Health Log Analytics generates several types of alerts.").

## Summary {#hla-op-ovrvw-tab-comp-based-alerts-sow__section_wkm_bkw_wtb}

Identified issue

:   This card describes the issue that led to the alert. The identified issue appears
    on the card and in the title for the alert. Information about the alert appears in
    the banner.

    Figure 1. Identified issue

    Select View surrounding logs to view log messages that are
    relevant to the alert. See [Analyze log lines that surround an anomaly in Health Log Analytics](https://www.servicenow.com/docs/jowNkkaSHojuKEIc9T7qjQ "View the log lines around an anomaly to help you identify the root cause of a Log Analytics alert.").

Anomaly

:   This card illustrates the anomalous activity that led to the alert.

    * The blue line shows the recent anomalous activity.
    * On some charts, the lightly shaded area indicates the expected (learned baseline) behavior.A peach-shaded area represents the
      baseline values for the same hour one day earlier. A pink-shaded area shows
      the values for the same period in the previous week.

    {#hla-op-ovrvw-tab-comp-based-alerts-sow__ul_jdh_wdm_4tb}

    In this example, the peach-shaded area shows the data for the same hour one day
    earlier. The drop in the metric value (events per minute) is clearly visible.  
    Figure 2. Anomaly card

    For more information on the kinds of anomalies that you might encounter, see [Types of anomalous behavior in Health Log Analytics](https://www.servicenow.com/docs/KjefGfKnKk8K2HvH_ZmU3Q "Anomalous behavior in a CI or a service can indicate an important issue. For example, a spike in the frequency or number of messages of a particular type can indicate a problem.").

## Impact {#hla-op-ovrvw-tab-comp-based-alerts-sow__section_ydf_dkw_wtb}

Configuration Items
:   This card provides information about the CIs that are impacted by the alert.

Impacted services
:   This card provides information about the services that are impacted by the alert.  
    Figure 3. Impact section

## Cause {#hla-op-ovrvw-tab-comp-based-alerts-sow__section_lgd_2kw_wtb}

Meaningful log properties
:   On this card, each bar chart shows the distribution of values for a single log property that
    contributed to the anomaly. Each property value is associated with a color. The length
    of a color bar correlates to the percentage that the property value holds in
    comparison with all other values for the property.  
    Figure 4. Meaningful log properties