Alarms are notifications that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client:
Name and description – Provides an identifying label and description.
Targets – Defines the type of object that is monitored.
Alarm Rules – Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms.
Last modified – The
...
last modified date and time of the defined alarm.
JetStream DR alarms have the following severity levels:
Info/Normal (or unknown)
Warning
Error/Critical
Alarm definitions are associated with the object selected in the inventory. An alarm monitors the type of inventory objects specified in its definition.
| Info |
|---|
Learn more about monitoring events, alarms and automated actions in vSphere. |
| Note |
|---|
Learn how to troubleshoot various issues signaled by JetStream DR alarms. |
List of JetStream DR Alarms
The following list describes conditions and methods to trigger various JetStream DR alarms which may can be helpful for troubleshooting and testing purposes.
“State” events (unmarked) and “email” events and both serve the same purpose but are reported differently by the system. State events are displayed as a banner announcement in vCenter, while email events appear under the Monitoring tab and trigger email notification, if configured.
DRVA Restarted
Reboot the DRVA VM or restart the DRVA service.
An alarm will be triggered and can be viewed from DRVA VM > Monitor > Events.
...
If the incoming VM network speed is high compared to the outgoing replication traffic, this can create cause "backpressure" leading to the alarm being triggered.
...