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


---

# Overview tab for a Log Analytics group

# Information on the Overview tab for a Log Analytics group {#ariaid-title1}

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

The alert Overview tab in Health Log Analytics helps you understand Log Analytics groups.

## Sections on the Overview tab for Log Analytics groups {#hla-op-ovrvw-tab-log-anltcs-alerts__section_gqn_fqp_3nb}

For a detailed description of Log Analytics groups, see [Types of Health Log Analytics alerts](https://servicenow-prod.fluidtopics.net/wyhSBPwW96jRO1m_dsi4BQ "Health Log Analytics generates several types of alerts.").

Correlations banner

:   During initial analysis, alerts are scored. Each correlation in the alert's log data with another alert contributes to the score. The higher the score, the more likely the alert is to be included as a Log Analytics
    alert in a Log Analytics alert.

    The following kinds of data are considered when determining whether alerts are correlated:

    * Time: The events all occurred within a configured time interval.
    * Metadata: The alerts have matching values in log-line metadata. For example, all alerts involve the same host.
    * Message text: The message text in the log data is similar or identical between alerts.
    * Trend: The alerts show a similar tendency in values or rates. For example, a particular metric value is increasing in all alerts.

    {#hla-op-ovrvw-tab-log-anltcs-alerts__ul_il5_bms_znb}  
    Click the More info link on the Correlations banner to view the list of correlations that relate the Log Analytics alerts.Abbildung : 1. Correlations banner ![Click More info to open the Correlations list.]() Abbildung : 2. Correlations

    1. List of correlations: The first correlation in the list is expanded to show the individual Log Analytics alerts that are correlated and the log correlator that the alerts share. The number in parentheses is the number of alerts in the correlation.
    2. An individual log correlator: The identifier for a group of correlated Log Analytics alerts. The alerts are grouped by the log-line data or metadata that is common to the alerts (for example, IP address, host name, or user name). The number in parentheses indicates the number of correlated alerts.
    3. Log Analytics alerts that are correlated.
    {#hla-op-ovrvw-tab-log-anltcs-alerts__ol_ftp_ypy_lnb}

Alerts in group

:   For a Log Analytics alert (Alert0010166 in the example), the Alerts in group section shows the Log Analytics alerts that are grouped under the Log Analytics alert.

    Click a Log Analytics alert to view its details. To view the full list of Log Analytics alerts, click View more or click the Alerts in group tab.  
    Abbildung : 3. Viewing alert details

Configuration Items
:   To view more detailed information on the CIs that are associated with the alerts,
    click the Configuration Items tab or click View more in the Configuration Items section. See [Operator phase 1: Analyze and acknowledge an alert](https://servicenow-prod.fluidtopics.net/_aBn0l_Aw1fS_oBGD8EZ9A "As an Event Management operator, the first thing you should do is access alerts and then find the ones you want to focus on. You can open the Alert form to analyze the details, and then acknowledge it to let other operators know that the issue causing the alert should be addressed in some way.").

Impacted services
:   To view detailed information on the services that are impacted by the alerts, click
    the Impacted services tab. See [Operator phase 1: Analyze and acknowledge an alert](https://servicenow-prod.fluidtopics.net/_aBn0l_Aw1fS_oBGD8EZ9A "As an Event Management operator, the first thing you should do is access alerts and then find the ones you want to focus on. You can open the Alert form to analyze the details, and then acknowledge it to let other operators know that the issue causing the alert should be addressed in some way.").
* **[Log Analytics alerts on the Alerts in group tab](https://servicenow-prod.fluidtopics.net/u7~shFCGkCC4OV~mJYfgPg)**   
  The table describes the Log Analytics alerts in a Log Analytics group on the Alerts in group tab.