Reference Guide

Column Description
Host Name It represents IP address or network name of the remote host.
Creation Date (UTC) Date and time when the alert got generated.
Last Updated (UTC) Date and time when the status of the alert is last changed.
User Note It shows the notes which are added through user.
Alert states
The alerts can be in any of the following states:
OPEN
It represents the state when an alert has been raised. When the alert is raised, the state remains open until the user closes or
acknowledges it from the UI, or the system generates a clear event that represents the issue has been resolved.
CLOSED
The user can move an alert to closed state after resolving the issue, or the system generates a clear event that represents the
issue has been resolved.
If the alert is closed from the UI, then its state changes to CLOSED, and the Last Updated time is updated but the severity
remains the same.
If the platform alert is closed through a system-generated event, then its severity changes to CLEAR along with the state
change to CLOSED, and the Last Updated time is updated.
The Operational Alerts are closed automatically after four hours. If node or director reboots, or NDU is performed within this
four hours interval, then Operational Alerts remain open even after four hours.
The Hardware alerts state change to closed state after moving to historical alerts.
ACK
Once the user feels that the message has been checked and there are no functional consequences because of the issue, then
the user can move an OPEN alert to the ACK state. Acknowledging an alert does not indicate that the issue has been resolved,
but it means that the user is aware to bear the consequences caused through the underlying issue with that alert.
Scope of the events
This property is limited to the platform alerts, and the scope of the events is categorized as:
● Director Scope
● Cluster Scope
Cluster scope-The cluster scope events are published only through one director which is the publisher. So, the cluster scope
alerts are seen only on the publisher at both the clusters. It means that only one director at each cluster shows these cluster
level alerts. If the publisher faces a node restart, then the other node becomes the publisher, and continue to serve as publisher
even after the previous node comes up.
Director scope-The director scope alerts can be seen on any of the nodes with respective director names as the component.
Change of publisher
There is a unique ID assigned to each of the directors and cluster. It is internally termed as scope incarnation.
8
Events and Alerts