---
sourceDocument: Xanadu IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-operations-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# View the list of Log Analytics alerts in a Log Analytics group

# View the list of Log Analytics alerts in a Log Analytics group {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

View the list of all Log Analytics alerts in a Log Analytics group on the Related records tab.

## Before you begin

Role required: evt_mgmt_operator, or evt_mgmt_user, or evt_mgmt_admin

## About this task

For a detailed description of Log Analytics groups and Log Analytics alerts, see [Types of Health Log Analytics alerts](https://www.servicenow.com/docs/d~tmO0MmkgntF50WCv3pgQ "Health Log Analytics generates several types of alerts.").

## Procedure

1. On the Overview tab for a Log Analytics alert, go to the Alerts in group card and select the View all link.  
   The Alerts in group section on the Related records tab displays.  
   Figure 1. Alerts in group section on the Related records tab
2. For each Log Analytics alert in the Log Analytics group, the information described in the table is available.  
   {#hla-op-alerts-in-group-sow__table_bcp_syz_4tb__entry__2}

   | Column | Description |
   |-|-|
   | Number | The number of the alert. Select the number to view detailed information for an alert. This field is automatically set. |
   | Initial event generation time | The time when the event that generated the alert first occurred. Note: Time here is the ServiceNow processing time, not the source system time. |
   | Group | Type of group that the alert belongs to: a standalone Log Analytics alert or a Component-based alert. |
   | Description | Anomalous pattern or metric that caused the alert to be generated. |
   | Severity | Severity value for the alert. The available values are: * Critical: Immediate action is required. Either the resource is not functional or critical problems are imminent. * Major: Major functionality is severely impaired or performance has degraded. * Minor: Either performance has degraded or there is a partial, non-critical loss of functionality. * Warning: Attention is required even though the resource is still functional. * Info: An informational message. An alert is created, but the resource is still functional. * Clear or Resolved: No action is required. An alert is not created from this event. Existing alerts are closed. {#hla-op-alerts-in-group-sow__ul_vmx_h5t_hdb} |
   | Priority group | Priority group that indicates the order in which to resolve alerts. Choices are as follows: * Urgent * High * Moderate * Low {#hla-op-alerts-in-group-sow__ul_nct_h3f_vmb} The priority group value is more important than severity alone. For example, a high priority and low severity alert should be addressed before a low priority and high severity alert. For information on how priority is calculated, see [Alert priority](https://www.servicenow.com/docs/ne~G~VZE5L91hA8xIao6eQ "Determine the order in which to handle alerts according to the alert priority score. Multiple factors determine the alert priority score and this value changes with changes to the underlying factors."). |
   | State | Processing state of the alert. A newly generated alert is in the Open state. Other states are as follows: * Reopen: A previously closed alert is open again, and it requires your attention. * Flapping: The alert is receiving identical events from the same source at high frequency. This state can cause an alert to re-open from the Closed state, resulting in a high frequency of changes between Open and Closed states. * Closed: The alert is closed and does not require any further action. You close an alert when it is remediated. {#hla-op-alerts-in-group-sow__ul_wmx_h5t_hdb} |
   | Configuration item | CI in the CMDB. The CI is applied to by the alert. |
   | Node | Node field that is received in the log message. The event described in the log message occurred on this node. Often, the node is the name of the CI that is associated with the alert. For example, a computer name, IP address, FQDN, or MAC address. |
   | Source | All Health Log Analytics alerts have the value Log Analytics in the Source column to indicate that the Health Log Analytics app generated the alert. |
   | Metric name | Name of the metric whose anomalous behavior led to the alert. For example, the I/O request in the case that the I/O request took longer than 15000 ms to complete. |
   | Updated | Most recent time when the alert information or state was updated. |
   [Table 1. Alerts in group]

   {#hla-op-alerts-in-group-sow__table_bcp_syz_4tb}
{#hla-op-alerts-in-group-sow__steps_up2_ytr_4tb}