Using Cloud Eye to Monitor the Health Status of Snt9B23 Supernodes

Constraints

• This solution is implemented based on Cloud Eye alarm rules. As an account can create a maximum of 100 alarm rules on Cloud Eye, at most 100 supernodes can be monitored.
• Cloud Eye host monitoring agency needs to be enabled as the alarms are generated based on Cloud Eye fault detection events. You can enable this agency when purchasing the supernode or create the agency on the Cloud Eye console after the purchase. For details, see Permissions.
• Alarm notifications are sent via SMS messages and emails using Simple Message Notification (SMN). There will be certain fees. For details, see Product Pricing Details.

Procedure

1. Log in to the Cloud Eye console.
2. Create an alarm rule template.

   Table 1 Parameters

   Parameter	Recommended Value
   Name	You are advised to name the template after the fault severity, for example, Subhealthy supernode.
   Alarm Type	Event
   Method	Select Configure manually. The recommended settings for other parameters are as follows: Event Name: Select the target events by referring to Using Cloud Eye to Monitor NPU Resources of a Single Lite Server Node. Alarm Policy: Generate the alarm once if the event occurs four times within 5 minutes. Note: Improper configurations may cause too many alarms or slow response. Alarm Severity: Select Major.

3. Create an alarm rule.

   Table 2 Alarm rule parameters

   Parameter	Recommended Value
   Name	You are advised to name the alarm rule in the <Supernode-name>_<Fault-level> format, for example, SuperPod_01_Subhealthy.
   Alarm Type	Event
   Event Type	System event
   Event Source	Elastic Cloud Server
   Monitoring Scope	Specific resources
   Instance	All subnodes in the supernode. Click Select Specific Resources, search for the supernode name, select all, and click OK.
   Method	Configure manually
   Alarm Policy	Enable Use Template and select the alarm template created in 2 from the drop-down list.
   Alarm Notifications	(Optional) Enable this if you want to receive alarm notifications by SMS, email, HTTP, or HTTPS. Note: SMN charges you for SMS, email, HTTP, and HTTPS messages. For details, see Product Pricing Details.
   Recipient	(Optional) This parameter is available only when Alarm Notifications is enabled. You are advised to create a topic.
   Notification Window	(Optional) This parameter is available only when Alarm Notifications is enabled. The default value is recommended.
   Trigger Condition	(Optional) This parameter is available only when Alarm Notifications is enabled. The default value is recommended.
   Enterprise Project	Set this parameter based on the real-life situation.

4. (Optional) Create a topic.

   Table 3 Parameters for creating a topic

   Parameter	Recommended Value
   Topic Name	Enter a name in English, for example, SuperPod-Sub-Health.
   Display Name	Name displayed in the email subject. Set it to the fault severity, for example, Subhealthy supernode.
   Enterprise Project	Set this parameter based on the real-life situation.

5. (Optional) Add a subscription. After creating a topic, add subscriptions to receive alarm notifications.

   Then, the terminal will receive a subscription confirmation. Confirm the subscription to receive alarm notifications.

Email Alarm Notification Example

In an alarm notification email, the subject displays the alarm severity, the content displays key information such as the alarm object, alarm policy, and alarm time. The alarm rule contains the name of the supernode to which the fault object belongs. For details about how to handle alarms, see Supported Events.

Querying Alarm Records

You can query alarm records through APIs. For details, see Alarm Records.