ZWatch
ZWatch, known as ZWatch monitoring system, allows you to monitor time series data and events. With ZWatch, alarm messages are pushed to the specified endpoints via SNS. ZWatch provides three types of alarm: resource alarm, event alarm, and third-party alarm, and supports the following types of endpoint: system endpoint, email, DingTalk, HTTP application, short message service, and Microsoft Teams. To use some specific resource alarms, install an agent.

Basic Workflow
- ZWatchZWatch provides the following features:
- Time series monitoring: Currently, monitors the following two types
of time series data:
- Resource load data: Provides a visual display of VM CPU utilizations and host memory utilizations.
- Resource capacity data: Provides a visual display of used IP counts and the total number of the running VM instances.
- Event collection: Collects predefined events triggered on the Cloud, such as the host disconnection and enabling the VM HA feature.
- Alarming: Triggers alarms for time series data or events.
- Audit: Records all operations and lets you to conduct searches for these operations.
- Customization: Customizes alarm settings and alarm SNS text
templates.
- Alarm: Currently supports the following two types of
alarm:
- Resource alarm: Triggers alarms for time series data. For example, sets an alarm for VM CPU utilizations. Specifically, when the CPU utilization of a VM instance exceeds 80% for 5 consecutive minutes, an alarm notification will be sent to your email.
- Event alarm: Triggers alarms for events, known as event subscriptions. For example, subscribes an event of the host disconnection. And then an alarm notification will be sent to your DingTalk when a host is disconnected.
- Third-party alarm: Receives alarm messages from third-party message sources. For example, when the storage pool of an enterprise storage is degraded, a system alarm will be triggered on the Cloud.
-
An SNS text template is a text template that is used when an alarm or event sends messages to an SNS topic.
- The Cloud contains a default template of an alarm message and a recovered message. If you do not create a template, the Cloud will use the default template.
- You can create multiple message templates, but can only default one template. Specifically, when messages are sent, the default formatted message will be used.
- With
${}
, you can use variables provided by an alarm or event in the template. - Currently, an SNS text template supports four types of endpoint platform: email, DingTalk, Microsoft Teams, and short message service. If you use an SNS text template, formatted alarm messages will be sent to you via email, DingTalk, Microsoft Teams, or short messages.
-
Message Source is used to connect with 3rd-party message sources, takes over 3rd-party alarm messages, and uniformly pushes these messages to various endpoints, whereby achieving unified managements and enhancing operations and maintenance efficiencies for these alarm messages. Currently, Message Source lets you take over alarm messages of Enterprise edition storages.
- Alarm: Currently supports the following two types of
alarm:
- Time series monitoring: Currently, monitors the following two types
of time series data:
- SNS
Notification services will push alarm messages to an endpoint, including a system endpoint, email, DingTalk, HTTP application, short message service, and Microsoft Teams.
Endpoint setting:- By default, the Cloud provides a system endpoint. If an alarm binds a system endpoint, you are prompted for alarm notifications displayed near the Messages button at the upper right in the UI.
- You can also create an email, DingTalk, HTTP application, short message service, or Microsoft Teams endpoint as needed.
Feature Benefits
- Provides a diversity of alarm metric items to monitor core resources and events on the Cloud in a comprehensive, fine-grained, and flexible manner.
- Supports five types of subscription theme: email, DingTalk, HTTP application, and short message service. Select an appropriate alarm theme as needed.
- One alarm can monitor multiple resources simultaneously.
- Endpoints such as email, DingTalk, and short message service let you to customize the alarm SNS text template. To quickly locate key information from alarm messages, set the alarm SNS text template as needed.
Typical Usage Scenario
ZWatch monitors core resources and events on the Cloud, and sets the alarm receiving mechanism. When core resources are abnormal, ZWatch will initiate real-time responses according to alarm levels, where O&M personnel can quickly locate and then solve problems.
More Information
- The monitoring data retention cycle defaults to 6 months. You can customize your
monitoring data retention cycle as needed. Method:
In the UI, choose Retention time of Monitoring data, and click the Edit icon. Default value: 6. Unit: month. Value range: 1-12, integer.
, locate - The monitoring data retention size defaults to 50 GB. You can customize your
monitoring data retention size as needed. Method:
In the UI, choose Retention size of Monitoring data, and click the Edit icon. Default value: 50 GB. We recommend that you set your retention size as needed.
, locate - ZStack Private Cloud can receive third-party alarms. To use the third-party alarm feature, go to , and turn on the Switch for Third-Party Alarm.