Alert attributes
Each Cloud Pak for Data System alert has a set of mandatory attributes, optional attributes that are common to multiple alerts, and alert-specific attributes.
The following attributes are included in every alert.
Following are the attributes that pertain to the status of the alert.
Attribute Name | Description |
---|---|
ID | Alert identifier. Each alert instance has its own unique identifier, starting from 1001. |
Type | High-level alert type, for example, HW_NEED_ATTENTION. For a list of types, see System hardware alerts and System software alerts. |
ReasonCode | A numeric value that determines the exact reason for rising the alert. For example, 502 means application start-up timeout. For a list of types, see System hardware alerts and System software alerts. |
Group | Indication of whether the alert is hardware related (HW) or software related (SW). |
Title | Descriptive title of the alert. |
Date | Time stamp that specifies when the alert was created. |
Close Date | The date when the alert was closed. This attribute pertains only to stateful alerts, that is, issues. |
Target | Determines the resource (device or service) for which the alert is reported. |
Target Type |
Identifies the type of component pointed by Target attribute. |
Severity |
Identifies the alert severity. The value can be:
|
Referenced Alert ID | An ID of another alert that is related to the selected alert. |
Attribute Name | Description |
---|---|
State | Alert processing state
|
SMTP Status | Status of sending SMTP notification:
|
Call Home Status | Status of sending Call Home notification:
|
Log Collection Status | Status of automatic log collection:
|
Log File Name | Name of tarball tar.gz with collected logs |
Log File Node | Node on which the log file is stored |
SRID | Service request ID from Call Home |
why is the status DELIVERED when delivery failed?