Elastic MapReduce (EMR) has been connected to Cloud Monitor (CM). You can configure alarm policies for EMR nodes and service monitoring metrics in the CM console.
- EMR has been connected to CM's default alarms. CM will automatically create a default alarm policy. For information about metrics/events or alarm rules supported by the EMR default policy, see Default Alarm Policy.
- You can manually create an alarm policy and set it as the default alarm policy. After the default policy is set, newly purchased instances will be automatically associated with the default policy without requiring manual addition.
|Configuration Type||Configuration Item||Description|
|Basic information||Policy name||Custom policy name|
|Remarks||Custom policy remarks|
|Monitoring type||Supported cloud service monitoring type|
|Policy type||Select the desired policy type for monitoring Tencent Cloud services.|
|Project||You can filter to find alarm policies under a project in the alarm policy list.|
|Alarm rule configuration||Alarm object||
|Trigger condition||Manual configuration (metric alarm)||Trigger condition: consists of metric, comparison, threshold, statistical period, and the number of consecutive periods. You can expand the trigger condition to view the metric trend, and based on which, set a proper threshold.|
|Manual configuration (event alarm)||Create an event alarm policy to get notifications in case of service resources or underlying infrastructure exceptions.|
|Select template||Select a configured template in the drop-down list. For more information, see Configuring Trigger Condition Template.|
|Configure alarm notification (optional)||Notification template||You can use the preset notification template (alarms will be notified to the root account administrator via SMS and email. This template is selected by default.) or customize one. Up to three notification templates can be bound to each alarm policy. For more information about notification template configuration, see Creating Notification Template.|