Skip to main content

Manage alarms

Alarm management enables you to view and manage alarms on the management platform.

Restrictions and guidelines

In RBAC mode, only a system administrator can manage host resource, VM resource, cluster resource, failure, network suboptimal health, and alarms for other anomalies. A security administrator can manage security alarms. A security auditor can view all alarms.

Features

• Manage real-time alarms

• Manage alarm thresholds

• Manage ignored alarms

• Manage alarm notifications

Manage real-time alarms​

Perform this task to filter, ignore, view, confirm, or clear alarms generated most recently. Expired

real-time alarms are moved to the history alarm list.

Restrictions and guidelines

• By default, the system refreshes the alarm information page every 10 seconds. Configure an appropriate refresh interval to ensure that operators can confirm the alarms before the page is refreshed.

• If a host only acts as a management platform and is not incorporated by the management platform, the alarms about the CPU usage and memory usage of the host cannot be ignored.

Filter alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Configure the filter parameters (see "Parameters"), and then click Filter. The matching alarms are displayed.

  4. To set the alarm list refresh interval, select an option from the Refresh Interval list.

View history alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Click the Historical Alarms tab.

  4. Configure the filter parameters (see "Parameters"), and then click Filter. The matching alarms are displayed.

  5. To set the alarm list refresh interval, select an option from the Refresh Interval list.

Ignore alarms

Perform this task to add real-time alarms that do not require attention to the ignored alarm list. Do not ignore or delete real-time host multipath exception alarms. If you ignore or delete such alarms, the storage operations center cannot synchronize the storage link status, causing link status inconsistency and failure.

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Click Ignore in the Actions column for the target alarm.

  4. Enter a description, and then click OK.

Display detailed information about an alarm

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Click the alarm information in the Contents column of the target alarm.

Confirm alarms

Perform this task to confirm the specified alarms. After you confirm an alarm, the state of the alarm changes to Confirmed. To confirm alarms:

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Select the target alarms, and then click Confirm.

Delete alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Select the target alarms, and then click Delete.

  4. In the dialog box that opens, click OK.

Edit alarm solution and remarks

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Click the alarm information in the Contents column of the target alarm.

  4. Click Edit Maintenance Experience.

  5. Enter the solution and remarks for the alarm.

  6. Click OK.

Clear alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarms.

  3. Click Clear.

  4. Select the severity, type, start time, and end time.

  5. Click OK.

Parameters

• Refresh Interval: Select the interval at which the alarm list is refreshed. Options include 5 Seconds, 10 Seconds, 30 Seconds, 1 Minute, and 5 Minutes.

• Severity: Select an alarm severity. Options include All, Critical, Major, Minor, and Info.

○ Critical: A failure affects the services provided by the system and requires immediate action. For example, an unavailable device or resource requires recovery. You must handle a critical alarm immediately even if it occurs during non-working hours.

○ Major: A failure degrades service quality and requires urgent action. For example, the service quality of a device or resource is degraded and must be restored. You must handle a major alarm immediately during working hours.

○ Minor: A failure does not degrade service quality. To prevent it from worsening, further observation or action at an appropriate time is required.

○ Info: A potential error might affect services, and evaluation is required before action is taken.

• Type: Select an alarm type. Different types indicate alarms from different sources.

• Source: Information about the source device of the alarm, including the device type, device name, and management IP address.

• Contents: Detailed content of the alarm.

• Last Triggered At: Last time when the alarm was generated.

• First Triggered At: First time when the alarm was generated.

• Alarm Count: Times the alarm has been reported.

• Impact: Possible impacts of the alarm.

• Alarm Cause: Reason why the alarm was generated. The reasons are predefined by the system and cannot be modified. This field displays the same information for the same type of alarms.

• Recommended Action: Remedies for the alarm. The remedies are predefined by the system and cannot be modified. This field displays the same information for the same type of alarms.

• Remarks: Processing experience and solution for the alarm, which are recorded by the operator. This field displays the same information for the same type of alarms.

Manage alarm thresholds​

An alarm threshold defines the minimum value of the specified metric that triggers an alarm. You can

set CPU usage, memory usage, disk usage, disk I/O throughput, and network throughput alarm thresholds.

Features

• Configure default thresholds

• Manage custom thresholds

Configure default thresholds​

Restrictions and guidelines

• By default, the management platform host operates as the alarm server. In an active-standby system, the active management platform host operates as the alarm server.

• To enable an alarm threshold, you must complete the configurations of the alarm threshold.

• The alarm threshold configuration takes effect in the priority order of VM, host, cluster, and O&M center. If you enable and configure the same alarm threshold for a VM, a host, a cluster, and O&M center, only the configuration with the highest priority takes effect.

• The CVK management platform does not have the VM escape alarm switch. However, the VM escape alarms can be automatically synchronized to the CVK management platform after you enable VM escape alarm on the Ops > Alarm Management > Alarm Thresholds > Default Threshold Settings > Security Alarms page of the management platform.

Display alarm threshold information

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. Click Collapse All to collapse the alarm thresholds configuration list by alarm types. Click Expand All to expand the entire alarm thresholds configuration list.

Edit an alarm threshold

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. Click Edit in the Actions column for a metric.

  4. Configure the parameters as described in "Parameters."

  5. Click OK.

Enable or disable an alarm threshold

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. To enable an alarm threshold, click Enable in the Actions column for an alarm threshold.

  4. To disable an alarm threshold, click Disable in the Actions column for an alarm threshold.

Bulk enable or disable alarm thresholds

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. Select the target alarm thresholds, and then select Enable or Disable.

  4. In the dialog box that opens, click OK.

Parameters

• Metric: Name of the alarm metric.

• Critical: Minimum value of the metric that triggers a critical alarm.

• Major: Minimum value of the metric that triggers a major alarm.

• Minor: Minimum value of the metric that triggers a minor alarm.

• Tip: Minimum value of the metric that triggers a tip.

• Duration: If the metric value keeps higher than the threshold for a time period specified by this parameter, the system generates an alarm. This parameter is available only for host resource alarms, VM resource alarms, and cluster resource alarms.

• Report Interval: Interval between two consecutive alarms of the same type for the same object. This parameter is available only for host resource alarms, VM resource alarms, cluster resource alarms, failure alarms, and network suboptimal health alarms.

• State: State of the alarm threshold.

• Severity: Severity of the alarm. Options include Critical, Major, Minor, and Tip. For a host resource, VM resource, or cluster resource metric, you must set the usage in percentage for that metric.

Manage custom thresholds​

After you configure and enable alarm thresholds for clusters, hosts, or VMs, you can view custom

thresholds and reset them to the default on the custom threshold management page. You can filter the custom thresholds by alarm type, alarm metric, and scope.

Restrictions and guidelines

• To manage custom thresholds, you must first configure and enable alarm thresholds for clusters, hosts, or VMs.

• If you configure both default and custom thresholds for clusters, hosts, or VMs, the custom thresholds take precedence over the default thresholds.

Reset custom thresholds

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. Click the Custom Threshold Settings tab.

  4. Select one or multiple custom thresholds, and then click Reset.

  5. Click OK.

View the configuration of a custom threshold

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Alarm Thresholds.

  3. Click the Custom Threshold Settings tab.

Manage ignored alarms​

Ignored alarm management enables you to ignore alarms that do not require attention. Ignored alarms

are not reported or displayed in the alarm list.

Restrictions and guidelines

If a host only acts as a management platform and is not managed by the management platform, the alarms about the CPU usage and memory usage of the host cannot be ignored.

Display alarm thresholds

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Ignored Alarms.

  3. Click the monitored item of an ignored alarm.

Filter ignored alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Ignored Alarms.

  3. Configure the filter parameters (see "Parameters"), and then click Filter. The matching ignored alarms are displayed.

Add an ignored alarm

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Ignored Alarms.

  3. Click Add.

  4. Configure the parameters as described in "Parameters," and then click Next.

  5. Select an object, and then click OK.

Delete ignored alarms

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Ignored Alarms.

  3. Select ignored alarms and then click Delete, or click Delete in the Actions column for an ignored alarm.

  4. In the dialog box that opens, click OK.

Manage alarm notifications​

Perform this task to promptly notify relevant personnel of alarms via multiple methods (such as email,

SMS, syslog, WeCom, and DingTalk) when the management platform detects an exception. This feature supports hierarchical alarm management, custom notification policies, and multi-channel delivery. It helps operations personnel promptly obtain system status and quickly respond to and handle faults, and effectively improves operations efficiency and system reliability.

Features

• Configure email notification parameters

• Configure SMS notification parameters

• Configure syslog notification parameters

• Configure WeCom notification parameters

• Configure DingTalk notification parameters

• Configure alarm servers

Configure email notification parameters​

Perform this task to enable the system to send email notifications for alarms to users.

Restrictions and guidelines

To enable the system to send email notifications, you must configure email parameters on the System > Parameters > Email Server page.

Procedure

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Configure the parameters as described in "Parameters."

  4. Click Email Server.

  5. Configure the parameters as described in "Configure the mail server," and then click OK.

  6. To check the email notification settings, click Email Test.

  7. To save the email notification settings, click Save.

Parameters

• Send To: Select the object to notify. Options include:

○ Users—Send alarms to the specified email addresses.

○ Send by Object Permissions—Send alarms to the email addresses of all operators in the same operator group as the alarm object. Make sure each operator in the group is configured with an email address.

• Concerned Objects: Select the hosts or VMs to be monitored by clicking Select Host or Select VM, respectively. If you select Selected for the Alarm Thresholds field, the system sends email notifications only when the selected objects generate alarms.

• Email Address: Enter the destination email address and click the icon to add the address to the list below. To delete a destination email address, select the address and click the icon. This field is available only when the object to notify is specified users.

• Severities: Select the severities of alarms to be monitored. Options include Critical, Major, Minor, and Info.

○ Critical—Indicates an issue that affects the services provided by the system and requires immediate action. For example, if a device or resource is unavailable, an action must be taken immediately, even if the failure occurs outside working hours.

Configure SMS notification parameters​

Perform this task to enable the system to send SMS notifications for alarms to the users.

Restrictions and guidelines

• To enable the system to send SMS notifications, you must configure SMS parameters on the System > Parameters > SMS page.

• When configuring SMS notification, you can specify multiple phone numbers to receive the alarms. If the system fails to send a message to multiple phone numbers, it prompts that the alarm sending failed to the first phone number, and then wait for a period of time (such as a few seconds or a few minutes) before prompting that the second phone number also failed to receive the alarm. Therefore, there may be a delay in the reporting time for failed SMS alarms.

Procedure

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the SMS tab.

  4. Configure the parameters as described in "Parameters."

  5. Click SMS.

  6. Enable SMS notifications, and then configure the parameters as described in "Configure SMS parameters."

  7. Click OK.

  8. To check the SMS notification settings, click SMS Test.

  9. To save the SMS notification settings, click Save.

Parameters

• Send To: Select the object to notify. Options include:

○ Users—Send alarms to the specified phone numbers.

○ Send by Object Permissions—Send alarms to the phone numbers of all operators in the same operator group as the alarm object. Make sure each operator in the group is configured with a phone number.

• Telephone Numbers: Enter the telephone number. This field is available only when the object to notify is specified users.

• Concerned Objects: Select the hosts or VMs to be monitored by clicking Select Host or Select VM, respectively. If you select Selected for the Alarm Thresholds field, the system sends SMS notifications only when the selected objects generate alarms.

Configure syslog notification parameters​

Perform this task to enable the system to send notifications for alarms to the specified syslog server.

Restrictions and guidelines

To enable the system to send syslog notifications, you must configure syslog server parameters on the System > Parameters > Syslog Server page.

Procedure

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the Syslog tab.

  4. Configure the parameters as described in "Parameters."

  5. Click Configure Syslog Server.

  6. Configure the parameters as described in "Configure the syslog server".

  7. Click OK.

  8. To check the syslog notification settings, click Test Connectivity.

  9. To save the syslog notification settings, click Save.

Parameters

• Severities: Select the severities of alarms to be monitored. Options include Critical, Major, Minor, and Info.

○ Critical—Indicates an issue that affects the services provided by the system and requires immediate action. For example, if a device or resource is unavailable, an action must be taken immediately, even if the failure occurs outside working hours.

Configure WeCom notification parameters​

This feature sends alarms in real time, which helps users obtain the platform operating status and fault

conditions in a timely manner. Integrating with WeCom, the system automatically sends various alarms to specific WeCom groups or individual users. This effectively improves alarm response efficiency and reduces operations risks. This feature supports flexible configuration of multi-level alarm types. Users can customize alarm severities, marks, types, and alarm objects as required for rapid fault location and handling.

Prerequisites

Before connecting the WeCom platform to the management platform, see the official WeCom configuration documentation and complete trusted IP address configuration. If you fail to do so, the system cannot correctly send alarms to WeCom.

Procedure

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the WeCom tab.

  4. Configure the parameters.

    ○ Send To App:

    ▪ Enterprise ID: Enter the enterprise ID.

    ▪ App ID: Enter the agent ID of the application created for receiving alarms.

    ▪ Secret: Enter the secret of the application created for receiving alarms.

    ○ (Optional.) Send To Bots:

    ▪ Bot Settings: Select or add WeCom group bots.

    ▪ Name: Customize the bot name.

    ▪ WebHook: Enter the Webhook URL of the WeCom group bot.

    ○ Severities: Select the severities of alarms to be monitored. Options include Critical, Major, Minor, and Info.

    ○ Mark: Select a mark for the alarm severity in the WeCom notification. For example, if you select the [] mark, the WeCom notifications for major and minor alarms start with [Major] and [Minor], respectively. If you select the <> mark, the WeCom notifications for major and minor alarms start with <Major> and <Minor>, respectively. Options include [], <>, and ().

    ○ Alarm Thresholds: Select the alarm thresholds to be monitored. Options include All and Selected. If you select Selected, you can click Add or Delete to add or delete alarm thresholds.

    ○ Concerned Objects: Select the hosts or VMs to be monitored by clicking Select Host or Select VM, respectively. To delete objects, select the target objects, and then click

Configure DingTalk notification parameters​

This feature sends alarms in real time, which helps users obtain the platform operating status and fault

conditions in a timely manner. Integrating with DingTalk, the system automatically sends various alarms to specific DingTalk groups or individual users. This effectively improves alarm response efficiency and reduces operations risks. This feature supports flexible configuration of multi-level alarm types. Users can customize alarm severities, marks, alarm thresholds, and alarm objects as required for rapid fault location and handling.

Procedure

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the DingTalk tab.

  4. Configure the parameters.

    ○ Send To App:

    ▪ Enterprise ID: Enter the enterprise ID.

    ▪ App ID: Enter the agent ID of the application created for receiving alarms.

    ▪ App Key: Enter the key of the application created for receiving alarms.

    ▪ Secret: Enter the secret of the application created for receiving alarms.

    ○ (Optional.) Send To Bots:

    ▪ Bot Settings: Select or add DingTalk group bots.

    ▪ Name: Customize the bot name.

    ▪ WebHook: Enter the Webhook URL of the DingTalk group bot.

    ○ Severities: Select the severities of alarms to be monitored. Options include Critical, Major, Minor, and Info.

    ○ Mark: Select a mark for the alarm severity in the DingTalk notification. For example, if you select the [] mark, the DingTalk notifications for major and minor alarms start with [Major] and [Minor], respectively. If you select the <> mark, the DingTalk notifications for major and minor alarms start with <Major> and <Minor>, respectively. Options include [], <>, and ().

    ○ Alarm Thresholds: Select the alarm thresholds to be monitored. Options include All and Selected. If you select Selected, you can click Add or Delete to add or delete alarm thresholds.

    ○ Concerned Objects: Select the hosts or VMs to be monitored by clicking Select Host or Select VM, respectively. To delete objects, select the target objects, and then click Delete. To export the resource information of the selected objects, click Export. If you select Selected for the Alarm Thresholds field, the system sends DingTalk notifications only when the selected objects generate alarms.

  5. Click Agent Settings. In the dialog box that opens, enable agent settings and configure related parameters.

    ○ Agent Settings: Select whether to enable agent settings.

    ○ Address: IP address or domain name of the agent server, used for communication with DingTalk interfaces.

    ○ Port: Port number of the agent server, used for communication with DingTalk interfaces.

    ○ Username: Authentication username of the agent server.

    ○ Password: Authentication password of the agent server, used together with the username for identity authentication.

  6. Click Test Agent to verify the DingTalk notification configuration.

  7. Click OK to return to the DingTalk notification configuration page.

  8. (Optional.) Click Cancel to cancel the current configuration and return to the DingTalk notification configuration page.

  9. Click Save to complete DingTalk notification configuration.

  10. (Optional.) Click Reset to restore the DingTalk notification configuration to the system defaults.

Configure alarm servers​

Perform this task to forward alarms generated by the management platform and its managed hosts to

third-party alarm servers (such as an upper-level alarm platform or operations monitoring system), which enables centralized alarm monitoring and management.

Add an alarm server

You can configure the network and protocol parameters of a third-party alarm server so that the platform can report alarms to it via SNMP.

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the Alarm Server tab.

  4. Click Add.

  5. Configure the third-party alarm server parameters:

    ○ IP Address: IP address of the third-party alarm server. As a best practice, specify an IP in the management network segment, for example, 192.168.1.1 or 2001::85b:3c51:f5ff:ffdb.

    ○ Port: Port number of the third-party alarm server.

    ○ Version: SNMP version used by the third-party alarm server. Options include SNMPv1 and SNMPv2c.

    ○ Read Community Name: Security string of SNMP used by the third-party alarm server to restrict who can read its information, which is similar to a password.

  6. Click OK.

  7. Click Save.

Delete a third-party alarm server

Perform this task to remove a third-party alarm server configuration so that the server no longer receives alarms from the platform.

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the Alarm Server tab.

  4. Click Delete in the Actions column for an alarm server.

  5. Click Save.

Save operation results

Perform this task to write operations such as the add and delete operations to the system so that the configuration can actually take effect.

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the Alarm Server tab.

  4. After you perform add or delete operations, click Save.

Reset third-party alarm servers

Perform this task to clear all third-party alarm server configurations in the system.

  1. On the top navigation bar, click Ops.

  2. From the left navigation pane, select Alarm Management > Notifications.

  3. Click the Alarm Server tab.