Elastic MapReduce
- Release Notes and Announcements
- Announcements
- Security Announcements
- Product Introduction
- Product release
- Purchase Guide
- EMR on CVM Billing Instructions
- EMR on TKE Billing Instructions
- EMR Serverless HBase Billing Instructions
- Getting Started
- EMR on CVM Operation Guide
- Planning Cluster
- Cross-AZ Cluster
- Configuring Cluster
- Administrative rights
- Managing Cluster
- Auto Scaling
- Disk Management
- Managing Service
- Configuration Management
- YARN Resource Scheduling
- Monitoring and Alarms
- Application Analysis
- Monitoring Metrics
- EMR on TKE Operation Guide
- Configuring Cluster
- Permission Management
- Cluster Management
- Service Management
- Configuration Management
- Monitoring and Ops
- Application Analysis
- EMR Serverless HBase Operation Guide
- 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
- Basic Hive Operations
- Advanced Usage
- Presto Development Guide
- Sqoop Development Guide
- Hue 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
- Ranger User Guide
- Kafka Development Guide
- StarRocks Development Guide
- Flink Development Guide
- Practical Tutorial
- Practice of EMR on CVM Ops
- Data Migration
- Practical Tutorial on Custom Scaling
- Practical Tutorial on Setting Scaling Rules
- API Documentation
- Making API Requests
- Cluster Resource Management APIs
- Cluster Services APIs
- FAQs
- EMR on CVM
DocumentationElastic MapReduceEMR Serverless HBase Operation GuideMonitoring and AlarmsConfiguring Alarms
Configuring Alarms
Last updated: 2024-11-28 16:22:15
Overview
Elastic MapReduce (EMR) has been connected to Tencent Cloud Observability Platform (TCOP). You can configure alarm policies for EMR nodes and service monitoring metrics in the TCOP console.
Directions
1. Log in to the TCOP console. In the left sidebar, choose Alert Management > Alert Configuration.
2. In the policy management page, click New Policy.
3. In the pop-up New Alert Policy window, see the table below to configure basic information, alarm rules, and create a notification template.
Configuration Type | Configuration Item | Description | |
Basic information | Policy name | | Custom policy name |
| Remarks | | Custom policy remarks |
Configure alarm policy | Monitoring type | | Select Cloud Service Monitoring |
| Project associated with policy | | After setting the project association, you can quickly filter alarm policies belonging to that project in the alarm policy list. |
| Policy type | | Select the desired policy type for monitoring Tencent Cloud products. |
| Alert object | | If you select an instance ID, the alarm policy will be bound to the selected instance. If you select an instance group, the alarm policy will be bound to the selected instance group. If you select all objects, the alarm policy will be bound to all instances that the current account has permission on. |
| Trigger condition | Manual configuration (metric alarm) | 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 and take appropriate actions in case of service resources or underlying infrastructure exceptions. |
| | Select template | Select the template button and select a configured template from the drop-down list. For specific configurations, see configuring trigger condition template. |
Configure alarm notification | Notification template | | By default, a preset notification template is bound (recipients are the main account administrators, and delivery channels are SMS and email). Up to three notification templates can be bound to each alarm policy. For more information about notification template configurations, see
New Notification Template. |
4. After the form is completed, click Complete.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No