When an E-MapReduce (EMR) cluster encounters resource contention or failures, you need timely notification to investigate and respond. CloudMonitor lets you define threshold-based alert rules that automatically send notifications when a metric crosses a threshold you set.
Prerequisites
Before you begin, ensure that you have:
-
An E-MapReduce cluster
Create an alert rule
-
Log on to the CloudMonitor console.
-
In the left navigation pane, choose Alerts > Alert Rules.
-
On the Alert Rules page, click Create Alert Rule.
-
On the Create Alert Rule page, configure the parameters described in the following sections. For more information, see Create an alert rule.
-
Click Confirm.
Scope
Define which resources the rule monitors.
| Parameter | Description |
|---|---|
| Product | From the Product drop-down list, select E-MapReduce. |
| Resource Range | The resources to which the rule applies. Valid values: All Resources (all EMR clusters in your account), Application Group (all clusters in a specific application group), Instances (specific clusters only). |
Alert condition
Define the metric and the trigger condition.
| Parameter | Description |
|---|---|
| Rule Description | The trigger condition for the alert. To configure it: click Add Rule, set Rule Name, Metric Type, Metric, Threshold, and Alert Level in the Configure Rule Description panel, then click OK. For example, you can trigger an alert when average CPU utilization is greater than or equal to 90% for 5 minutes and this condition persists for 3 consecutive checks. For the full list of supported EMR metrics, see E-MapReduce. |
| Mute Period | The interval at which alert notifications are resent for a persistent alert. Use this to suppress repeated notifications when an alert condition persists for an extended period. |
| Effective Period | The time window during which the rule is active. CloudMonitor checks monitoring data and sends alerts only within this window. |
Notifications
Configure who receives alert notifications. Notifications are sent when an alert is triggered (metric crosses the threshold).
| Parameter | Description |
|---|---|
| Alert Contact Group | The contact group that receives alert notifications. For instructions on creating a contact group, see Create an alert contact or alert contact group. |
| Alert Callback | A public URL to which CloudMonitor sends alert details via POST requests. Only HTTP is supported. |
| Tag | Key-value pairs for organizing and filtering alert rules. |
Automated actions (optional)
Trigger downstream services when an alert fires. These actions are executed each time an alert is reported.
| Parameter | Description |
|---|---|
| Auto Scaling | Enable this to trigger an Auto Scaling rule when an alert is reported. Specify the Region, ESS Group (Elastic Scaling Service group), and ESS Rule. For setup instructions, see Configure a scaling group and Configure a scaling rule. |
| Log Service | Enable this to send alert details to a Logstore in Simple Log Service when an alert is reported. Specify the Region, ProjectName, and Logstore. For setup instructions, see Quick Start: Use Logtail to collect and analyze text logs from an ECS instance. |
| Simple Message Queue (formerly MNS) - Topic | Enable this to send alert details to a topic in Simple Message Queue (formerly MNS) when an alert is reported. Specify the region and topic. For setup instructions, see Create a topic. |
| Function Compute | Enable this to send alert notifications to Function Compute for format processing when an alert is reported. Specify the region, service, and function. For setup instructions, see Quickly create a function. |
Advanced settings
Click Advanced Settings to configure the following parameter.
| Parameter | Description |
|---|---|
| Method to handle alerts when no monitoring data is found | Controls alert behavior when metric data is unavailable. Valid values: Do not do anything (default), Send alert notifications, Treated as normal. |