Log Analytics alerts on the Alerts in group tab
The table describes the Log Analytics alerts in a Log Analytics group on the Alerts in group tab.
| Column | Description |
|---|---|
| Number |
The number of the alert that appears in the list of alerts on the Operator Workspace dashboard.
To view detailed information for an alert on the Details tab, click the alert number. This field is automatically set. |
| 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:
|
| Priority group | Priority
group that indicates the order in which to resolve alerts. Choices are as
follows:
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. |
| State | Processing
state of the alert. A newly generated alert is in the Open
state. Other states are as follows:
|
| 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 Log Analytics alerts have the value Log Analytics in the Source column to indicate that Health Log Analytics 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. |