Viewing Events

To view events in VAST Web UI, select Alarms & Events and then Events to open the Events page.

Note
The event log holds the latest up to 1.5 million events.

For each event, the following information can be displayed:

Tip
To display or hide fields, click to the right of a column title, and then click to open a dropdown where you can select or unselect fields.

ID	The ID of the event.
Date	The date of the event.
Object Name	The name of the object involved in the event.
Message	A description of the event.
Event Type	The type of event that occurred. See Event Types.
Object Type	The type of the object involved in the event.
Origin	The initiator of the event. Possible values: Cluster Management Security User
Severity	The severity of the alarm triggered by the event. This setting is inherited from the event definition, and you can modify it. Possible values: Info. No alarm is raised. Minor. An alarm of minor severity is raised. Major. An alarm of major severity is raised. Critical. An alarm of critical severity is raised.

Aggregating Similar Events and Alarms

Alarms or events that are similar (but may originate in different objects of the same type) are aggregated, and appear as a single entry in the Alarms or Events tables. When alarms are aggregated, the Object Name shows the Cluster on which the alarm occurred. The message text will list the actual objects on which the event occurred.

For example, the following record shows an event that occurred a two CNodes:

vast17-kfs ALERT[P166625:E1:S255:Fa35e8 time="2024-05-07 23:01:13.049879590"]: A group with gid=1305910462 and name=vast-test-group-1305910462-0 and already exist in the map (new name=)vast-test-group-1305910462-1 counter: 7776. Occurred on cnode-3-9 (172.16.3.9) [v17cn1], cnode-3-8 (172.16.3.8) [v17cn2]

Note
Events and alarms are aggregated for ALARM and PANIC events only.

Filtering Hardware Events for Lower-Level Components

Hardware alarms and events for lower-level components (for example an SSD unit or a fan) are suppressed if they also trigger events for higher-level components (for example the CNode or DNode containing them). In this case, only the events for the higher-level component appear in the Events or Alarms table. So, for example, it alarms are generated for an SSD unit and the CNode containing it, the alarm for the SSD is suppressed, and only the alarm for the CNode appears.