Event Alarm

An event alarm mainly monitors system events, such as the VM state change event, and the host disconnected event. You can customize an event alarm.

Event Alarm Page

In the navigation pane of the ZStack Private Cloud UI, choose Platform O&M > ZWatch > Alarm > Event Alarm to enter the Event Alarm tab page, as shown in Event Alarm Page.
Figure 1. Event Alarm Page


On the Event Alarm tab page, the system provides a series of default event alarms as follows:
Default Event Alarm Description
Short Message Sent Error
  • By default, all short message endpoints on the Cloud are monitored.
  • If any short message endpoint cannot receive alarm messages, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Management Node Join
  • By default, all management nodes on the Cloud are monitored.
  • If any management node reconnects from the disconnected status, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Host Connected
  • By default, all hosts on the Cloud are monitored.
  • If any host reconnects from the disconnected status, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
vRouter Connected
  • By default, all routers on the Cloud are monitored.
  • If any router reconnects from the disconnected status, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Host Disconnected
  • By default, all hosts on the Cloud are monitored.
  • If any host is disconnected, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Backup Storage Connected
  • By default, all backup storages on the Cloud are monitored.
  • If any backup storage reconnects from the disconnected status, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Primary Storage Connected
  • By default, all primary storages on the Cloud are monitored.
  • If any primary storage reconnects from the disconnected status, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Primary Storage Disconnected
  • By default, all primary storages on the Cloud are monitored.
  • If any primary storage is disconnected, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Management Node Left
  • By default, all management nodes on the Cloud are monitored.
  • If any management node is disconnected, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Backup Storage Disconnected
  • By default, all backup storages on the Cloud are monitored.
  • If any backup storage is disconnected, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
vRouter Disconnected
  • By default, all routers on the Cloud are monitored.
  • If any router is disconnected, this alarm will be triggered.
  • By default, the Cloud notification will be triggered. After you bind an endpoint, you will receive alarm notifications via the endpoint.
Note:
  • By default, an event alarm allows you to change only the emergency level.
  • An event alarm allows you to add an endpoint and remove a newly added endpoint.
  • An event alarm does not allow you to remove system alarm endpoints and delete default event alarms.
  • If you upgrade the Cloud from an earlier version to 3.8.0, the emergency level of the default event alarms is Emergent. If you customize an event alarm, the emergent level is Major.

Create Event Alarm

Apart from the default event alarms provided by the Cloud, you can create event alarms as needed. On the Event Alarm tab page, click Create Event Alarm. On the displayed Create Event Alarm page, set the following parameters:
  • Resource Type: Select a resource type, including VM instance, vRouter, backup storage, management node, host, primary storage, vCenter, backup job, and project resource. Note that to add a project resource, you need to install the Enterprise Management license.
  • Metric Item: Select a metric item according to the resource type that you selected.
  • Emergency Level: Select an emergency level, including emergent, major, and information. Different levels of alarms will send out the corresponding levels of alarm messages.
  • Endpoint: Optional. If not selected, an endpoint is not specified. If selected, alarm messages will be sent to the specified endpoint.
    Note:
    • You can add multiple endpoints.
    • You can either select a system default endpoint or create an endpoint as needed.
    • For more information about how to create an endpoint, see Endpoint.
You can create an event alarm, as shown in Create Event Alarm.
Figure 2. Create Event Alarm


Note:
  • An event alarm will only be triggered once after an event happens, and does not allow you to set repeated alarms.
  • When any resource monitored by an event alarm recovers from the alarm status, recover messages will be sent for one time. You can set message contents on the SNS text template page as needed.
  • If an event alarm recovers from the alarm status and then continue to meet the alarm condition, this alarm will be triggered for one time again.

Event Alarm Operations

You can perform the following operations on an event alarm:
  • Create: Create an event alarm.
  • Add endpoint: Add an endpoint to the event alarm that you selected.
  • Remove endpoint: Remove an endpoint from an event alarm.
  • Delete: Delete an event alarm. Exercise caution. If you delete an event alarm, all resources on the event alarm will be deleted as well. This resource alarm will not be triggered.
  • Change: Change an emergency level of an event alarm, which is supported by default event alarms and custom event alarms.
  • Check alarm log: Set a time range to check alarm logs sent by the event alarm within the time range that you set.
  • Audit: Check related operations of this event alarm.