Overview of Alarms and Events

VAST Cluster logs system driven events, such as changes to object states and properties, and user driven events, such as the creation, modification or deletion of any object in the system. The events are predefined and you can modify those definitions of the events that are logged.

Events are logged with their timestamps and remain accessible until the event log exceeds its buffer size (1.5 million events) or time limit (30 days).

Most events are defined to trigger an alarm. The alarm severity is part of the event definition. For example, if a CNode fails, the failure is logged as an event, and an alarm of critical severity is raised.

You can define default and event-specific actions that are triggered when alarms are raised. These can include sending emails, sending the alarm information to an external application via a webhook, and sending alarms to a syslog server.

Alarms are removed automatically when the issue that triggered the event is resolved.  VAST Cluster features automatic recovery mechanisms to resolve issues that can arise.