tencent cloud

Elastic MapReduce

Release Notes and Announcements
Release Notes
Announcements
Security Announcements
Product Introduction
Overview
Strengths
Architecture
Features
Use Cases
Constraints and Limits
Technical Support Scope
Product release
Purchase Guide
EMR on CVM Billing Instructions
EMR on TKE Billing Instructions
EMR Serverless HBase Billing Instructions
Getting Started
EMR on CVM Quick Start
EMR on TKE Quick Start
EMR on CVM Operation Guide
Planning Cluster
Administrative rights
Configuring Cluster
Managing Cluster
Managing Service
Monitoring and Alarms
TCInsight
EMR on TKE Operation Guide
Introduction to EMR on TKE
Configuring Cluster
Cluster Management
Service Management
Monitoring and Ops
Application Analysis
EMR Serverless HBase Operation Guide
EMR Serverless HBase Product Introduction
Quotas and Limits
Planning an Instance
Managing an Instance
Monitoring and Alarms
Development Guide
EMR Development Guide
Hadoop Development Guide
Spark Development Guide
Hbase Development Guide
Phoenix on Hbase Development Guide
Hive Development Guide
Presto Development Guide
Sqoop Development Guide
Hue Development Guide
Oozie Development Guide
Flume Development Guide
Kerberos Development Guide
Knox Development Guide
Alluxio Development Guide
Kylin Development Guide
Livy Development Guide
Kyuubi Development Guide
Zeppelin Development Guide
Hudi Development Guide
Superset Development Guide
Impala Development Guide
Druid Development Guide
TensorFlow Development Guide
Kudu Development Guide
Ranger Development Guide
Kafka Development Guide
Iceberg Development Guide
StarRocks Development Guide
Flink Development Guide
JupyterLab Development Guide
MLflow Development Guide
Practical Tutorial
Practice of EMR on CVM Ops
Data Migration
Practical Tutorial on Custom Scaling
API Documentation
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
FAQs
EMR on CVM
Service Level Agreement
Contact Us

Alarm Configurations

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-23 14:29:38

Overview

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.
Note:
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.

Directions

1. Log in to the Cloud Monitor console and click Alarm Configuration > Alarm Policy on the left sidebar.
2. On the Alarm Policy page, click Create.
3. In the pop-up window, configure the basic information, alarm policy, and notification template as instructed below.
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
If you select an instance ID, the alarm policy will be associated with the selected instance.
If you select an instance group, the alarm policy will be associated with the selected instance group.
If you select all objects, the alarm policy will be associated all instances that the current account has permission on.
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.
4. Click Complete.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック