Alarm thresholds

An alarm threshold defines the minimum value of the specified indicator that triggers an alarm. You can set CPU usage, memory usage, and disk usage alarm thresholds for hosts, VMs, and clusters, and set disk throughput and network throughput alarm thresholds for hosts and VMs.

Alarm threshold management enables you to view the predefined alarm thresholds and configure the alarm server, alarm thresholds, and alarming state.

Application scenarios

Perform this task to customize the alarms that will be reported by the system.

Restrictions and guidelines

By default, the host that runs Space Console operates as an alarm server.
A minimum of one alarm server is required.
To enable an alarm threshold, you must complete the configuration of the alarm threshold.
Gateway alarms include:
- Gateway Connection Failure: Detects whether the gateway and Space Console have good connectivity. To enable this alarm, configure the gateway settings on the external services configuration page, including the gateway's internal IP address.
- Abnormal Gateway Status: Detects whether the gateway and the management node have good connectivity, or whether Nginx is running correctly on the gateway.
- Abnormal Network Connectivity Between Gateway and Service Nodes: Detects whether the gateway and port 22 (used by service nodes) have good connectivity.
- Abnormal Protocol Connectivity Between Gateway and Service Nodes: Detects whether the gateway and ports 5900 to 6400 (used by service nodes) have good connectivity.
- Gateway Isolation: Once enabled, the load balancer will isolate the faulty gateway and generate this alarm if a gateway has any of the following alarms:
  - Abnormal Gateway Status.
  - Abnormal Network Connectivity Between Gateway and Service Nodes.
  - Abnormal Protocol Connectivity Between Gateway and Service Nodes.
  Make sure you have completed load balancer configuration before enabling this alarm.
- Abnormal gRPC Connectivity Between Gateway and Controller Node: Detects whether the gRPC connection between the gateway and a controller node has timed out.
- Controller Node Isolation upon gRPC Communication Failure: Once enabled, the gateway will isolate the faulty controller node if an Abnormal gRPC Connectivity Between Gateway and Controller Node alarm is generated.
- To have a gateway alarm other than the Gateway Connection Failure alarm take effect, you must enable the gateway alarm monitoring service by executing the gateway monitor enable command at the gateway backend. For more information, see H3C Workspace Cloud Desktop Security Gateway Installation Guide (Office Scenario).

Configure alarm servers

Perform this task to specify a third-party alarm server to receive the alarm messages sent from Space Console and the managed hosts. Alarm servers must support and run the SNMP service. Before adding a new alarm server, make sure the SNMP community name is consistent with the SNMP settings of the third-party server that receives the alarms. You can configure a maximum of four alarm servers.

Procedure

From the left navigation pane, select Monitor Reports > Alarms > Alarm Thresholds.
Click Alarm Server Configuration.
Click Create, enter an IP address, port number (6162 by default), and SNMP community name. The default SNMP community name is private. Modify it as needed.
Click OK.

View alarm threshold settings

From the left navigation pane, select Monitor Reports > Alarms > Alarm Thresholds.
This page displays the predefined alarm threshold information. You can click Expand All to view the detailed alarm threshold settings.

Parameters

Alarm Type: Alarm type, including host resource alarms, VM resource alarms, cluster resource alarms, fault alarms, distributed storage resource alarms, desktop alarms, virtual applications alarms, endpoint alarms, VIP desktop alarms, gateway alarms, license alarms, and other alarms.
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.
Info: Minimum value of the metric that triggers an informational alarm.
Duration: If the metric value stays above the threshold for a time period specified by this parameter, the system generates an alarm. This parameter is required for host resource, VM resource, cluster resource alarms, desktop alarms, virtual application alarms, endpoint alarms, gateway alarms, and VIP desktop alarms.
Detection interval: Interval for detecting whether the alarm metrics reach the threshold. This parameter is required for desktop alarms, virtual application alarms, endpoint alarms, VIP desktop alarms, gateway alarms, and license alarms.
Alarm Interval: Report interval for a type of alarms for an alarm source. The default is 0 days. This parameter is required for host resource, VM resource, cluster resource, fault alarms, and other alarms.
State: State of the alarm threshold, including Enabled and Disabled.

Edit an alarm threshold

For client network delay alarms, the modifications will take effect only after the client restarts.

To edit an alarm threshold:

From the left navigation pane, select Monitor Reports > Alarms > Alarm Thresholds.
This page displays the predefined alarm threshold information. You can click Expand All to view the detailed alarm threshold settings.
Click Edit for an item to edit the threshold settings for the item and then click OK. For more information about parameters, see "Parameters."

Enable or disable an alarm threshold setting

From the left navigation pane, select Monitor Reports > Alarms > Alarm Thresholds.
Perform either of the following tasks:
- To enable or disable multiple alarm threshold settings, select the alarm threshold items, click More and then select Enable Indicators or Disable Indicators.
- To enable or disable an alarm threshold, click Enable or Disable in the Actions column for the target alarm threshold item.