Alarms

1. Log in to the console.
2. Click Service List and choose Cloud Eye under Management & Governance.
3. In the navigation pane, choose Alarm Management > Alarm Rules and click Create Alarm Rule. The Create Alarm Rule page is displayed.
4. Configure an alarm rule, as shown in Table 1.

   Table 1 Parameters

   Parameter	Description	Example Value
   Name	A name is randomly generated, or can be customized.	alarm-6a6a
   Description	Description of the alarm rule.	-
   Alarm Type	Alarm type that the alarm rule applies to. The value can be Metric or Event.	Event
   Event Source	Service for which the alarm rule is created.	Workspace
   Monitoring Scope	Application scope of the alarm rule. You can select All resources, Resource groups, or Specific resources. NOTE: If you select All resources, an alarm notification will be sent when any instance meets the alarm policy, and the alarm rule will be automatically applied to the newly purchased resources. If you select Resource groups, an alarm notification will be sent when any resource in the group meets the alarm policy. If you select Specific resources, click Select Specific Resources below. On the page displayed, select one or more resources and click OK.	All resources
   Method	Method of creating an alarm rule.	Configure manually
   Alarm Policy	Policy for triggering an alarm. If you set Resource Type to Website Monitoring, Log Monitoring, Custom Monitoring, or a specific cloud service, whether to trigger an alarm depends on whether the metric data in consecutive periods reaches the threshold. For example, Cloud Eye triggers an alarm if the average CPU usage of the monitored object is 80% or more for three consecutive 5-minute periods. If you set Resource Type to Event Monitoring, the event that triggers an alarm is an instant operation. For example, if the operating status is abnormal, an alarm will be triggered. NOTE: A maximum of 50 alarm policies can be added to an alarm rule. If any of these alarm policies is met, an alarm is triggered.	Add the following alarm policies: Abnormal desktop heartbeat Failure of assigning desktops in a desktop pool Desktop access failure Desktop startup failure Failure of automatic desktop pool capacity expansion Failure of dedicated host desktop migration Alarm Severity: Major
   Alarm Notification	Whether to send a notification after an alarm policy is configured.
   Notification Object	Object that receives alarm notifications. You can select the account contact or a topic. Account contact is the mobile phone number and email address of the registered account. A topic is a specific event type for publishing messages or subscribing to notifications. If the required topic is not available, create a topic and add subscriptions.	-
   Notification Window	Alarm notifications are sent only during the specified period. If Notification Window is set to 08:00-20:00, alarm notifications are sent only from 08:00 to 20:00.	-
   Trigger Condition	Condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.	Select Generated alarm. Select Cleared alarm.

   NOTE:

   Alarm notifications sent by SMN will be billed. For details, see Product Pricing Details.

5. In the Advanced Settings area, configure the enterprise project and tag.
6. After the configuration is complete, click Create.

Checking alarm records

NOTE:

• When alarms are reported to Cloud Eye, such as desktop heartbeat exceptions, and failures of desktop assignment, desktop access, desktop startup, desktop pool automatic capacity expansion, and dedicated host desktop migration, the account contact specified in Notification Object in Table 1 will receive a message.

• You can also check alarm records of all events on the Cloud Eye console.

1. Log in to the console.

2. Click Service List and choose Cloud Eye under Management & Governance.
3. In the navigation pane, choose Alarm Management > Alarm Records. The Alarm Records page is displayed.
4. Set Resource Type to Workspace to check all status events.
   NOTE:

   Event type classification:

   • Abnormal desktop heartbeat
   • Failure of assigning desktops in a desktop pool
   • Desktop access failure
   • Desktop startup failure
   • Failure of automatic desktop pool capacity expansion
   • Failure of dedicated host desktop migration

5. Click View Details to check the event information, as shown in Figure 1.
   Figure 1 Monitoring details