Realtime Compute for Apache Flink:Configure monitoring and alerting

CloudMonitor

Development console of Realtime Compute for Apache Flink

In the development console of Realtime Compute for Apache Flink, you can configure alert rules for metrics only for a single deployment. You can create an alert rule for a deployment directly or by using an existing alert rule template. The use of an alert rule template helps improve your configuration efficiency.

1. Go to the Alarm tab.

   1. Log on to the Realtime Compute for Apache Flink console. Find the workspace that you want to manage and click Console in the Actions column.

   2. In the left-side navigation pane, choose O&M > Deployments. Find the deployment that you want to manage and click its name.

   3. Click the Alarm tab.

2. On the Alarm tab, click the Alarm Rules tab. In the upper-right corner of the Alarm Rules tab, choose Add Rule > Custom Rule.

   You can also create an alert rule by using an alert rule template. To create an alert rule by using an alert rule template, choose Add Rule > Create Rule by Template, click the name of the template that you want to use, and then perform the subsequent steps. You can modify the template parameters based on your business requirements. This helps improve your configuration efficiency.

3. In the Create Rule panel, configure the parameters. The following table describes the parameters.

   Section	Parameter	Description
   Rule	Name	The name of the alert rule. The name must be 3 to 64 characters in length and can contain lowercase letters, digits, and underscores (_). It must start with a lowercase letter.
   	Description	The description of the alert rule.
   	Content	The conditions that trigger an alert. After you configure the conditions, Realtime Compute for Apache Flink compares the values of specified metrics with the thresholds that are specified in the conditions at the interval you specify. If one of the conditions resolves to true, an alert is triggered. Metric: Restart Count in 1 Minute: the number of times that the JobManager restarts deployments in 1 minute. Checkpoint Count in 5 Minutes: the number of times that checkpointing succeeds in 5 minutes. Emit Delay: the processing delay. This parameter specifies the difference between the time when data is generated and the time when data leaves the source operator. Unit: seconds. Important The time when the data is generated depends on the timestamp that is recorded in the external system. If no timestamp is recorded in the external system or the timestamp that is recorded when data is written to the external system is incorrect, the value of the Emit Delay parameter is invalid and cannot be used to determine the true processing delay. IN RPS: the number of input data records per second. OUT RPS: the number of output data records per second. Source Idle Time: the duration for which data is not processed in the source. Unit: milliseconds. Time Interval: the interval within which data of a metric is collected every minute. Realtime Compute for Apache Flink obtains data of the metric within the last interval and compares the obtained data with the specified threshold. If the historical data meets the specified conditions of the alert rule, an alert is triggered. Comparator: The greater-than-or-equal-to sign (>=) and the less-than-or-equal-to sign (<=) are supported. Thresholds: the value that is used to compare with the value of a metric. If you set the Comparator parameter to the greater-than-or-equal-to sign (>=), the maximum value of the metric on the vertical axis within the last interval is used. If the maximum value of the metric within the last interval is greater than or equal to the threshold, an alert is triggered. If you set the Comparator parameter to the less-than-or-equal-to sign (<=), the minimum value of the metric on the vertical axis within the last interval is used. If the minimum value of the metric within the last interval is less than or equal to the threshold, an alert is triggered. For example, you can set the Time Interval parameter to 5 minutes, the Comparator parameter to the less-than-or-equal-to sign (<=), and the Thresholds parameter to 2. In this case, Realtime Compute for Apache Flink obtains the values of a metric within the last 5 minutes on the vertical axis and compares the minimum value of the metric with the specified threshold. If the minimum value of the metric within the specified interval is less than or equal to the threshold, an alert is triggered.
   	Effective Time	The time period during which the alert rule is effective. If you do not specify a time period, all alert rules are effective throughout the day. For example, you can specify a time period from 09:00 to 18:00.
   	Alarm Rate	The interval at which an alert is reported. Unit: minutes. You can set this parameter to a value in a range from 1 minute to 1440 minutes (24 hours).
   Notification	Notification	The method that is used to send a notification. You can select multiple notification methods. Valid values: DingTalk Email SMS Webhook Phone Make sure that the contact you added can receive alert notifications. Otherwise, alert notifications cannot be sent. Click Notification object management on the right side of Notification object to check whether the phone number passes verification. If Unverified appears in the Phone column of a contact on the Contact tab, click Unverified to complete verification. Important Make sure that one or more contacts are created and added. Otherwise, alert notifications cannot be sent. For example, if you select DingTalk for the Notification parameter, a DingTalk chatbot must be added as a contact.
   	Notification object	The contacts to which alert notifications are sent. You can select multiple contacts. You can directly select or search for a contact. You must create contacts before you select contacts. To manage contacts, perform the following operations: Click Notification object management on the right side of Notification object. In the Edit Contact Group dialog box, click Edit in the Actions column on the Contact Group, Contact, Webhook, and DingTalk tabs separately, edit information, and then click Save. For more information about how to add a DingTalk or Lark chatbot and a webhook, see the FAQ section of this topic.
   	Alarm Noise Reduction	After you click Advanced Settings, you can turn on Alarm Noise Reduction. After you turn on Alert Noise Reduction, the system does not send alert notifications if a deployment can quickly resume due to a short-period failover. For example, in cluster scheduling or automatic tuning scenarios, a deployment may perform a failover for a short period of time. The system sends alert notifications only when the specified threshold condition is continuously met.
   	No Data Alarms	After you click Advanced Settings, you can turn on No Data Alarms and specify the time period during which no data is generated. After you turn on this switch, data that is monitored based on codeless tracking is reported. If no data is reported during the specified time period, the system sends an alert notification. In most cases, if an issue, such as an exception of the JobManager, abnormal deployment cancellation, or an exception of the report trace, occurs, data that is monitored based on codeless tracking is reported.

4. Click OK.

   After you create an alert rule, the rule is immediately effective. You can stop, edit, or delete the alert rule in the alert rule list.

ARMS

CloudMonitor

Development console of Realtime Compute for Apache Flink

In the development console of Realtime Compute for Apache Flink, you can configure a deployment failure-triggered alert rule only for a single deployment.

1. Go to the Alarm tab.

   1. Log on to the Realtime Compute for Apache Flink console. Find the workspace that you want to manage and click Console in the Actions column.

   2. In the left-side navigation pane, choose O&M > Deployments. Find the deployment that you want to manage and click its name.

   3. Click the Alarm tab.

2. On the Alarm tab, click the Alarm Rules tab. In the upper-right corner of the Alarm Rules tab, choose Add Rule > Custom Rule.

   You can also create a deployment failure-triggered alert rule by using an alert rule template. To create a deployment failure-triggered alert rule by using an alert rule template, choose Add Rule > Create Rule by Template, click the name of the template that you want to manage, and then perform the subsequent steps. This helps improve your configuration efficiency.

3. In the Create Rule panel, configure the parameters. The following table describes the parameters.

   Section	Parameter	Description
   Rule	Name	The name of the alert rule. The name must be 3 to 64 characters in length and can contain lowercase letters, digits, and underscores (_). It must start with a lowercase letter.
   	Description	The description of the alert rule.
   	Content	The metric to be monitored. In this example, Job Failed is selected.
   	Effective Time	The time period during which the alert rule is effective. If you do not specify a time period, all alert rules are effective throughout the day. For example, you can specify a time period from 09:00 to 18:00.
   	Alarm Rate	The interval at which an alert is reported. Unit: minutes. You can set this parameter to a value in a range from 1 minute to 1440 minutes (24 hours).
   Notification	Notification	The method that is used to send a notification. You can select multiple notification methods. Valid values: DingTalk Email SMS Webhook Phone Make sure that the contact you added can receive alert notifications. Otherwise, alert notifications cannot be sent. Click Notification object management on the right side of Notification object to check whether the phone number passes verification. If Unverified appears in the Phone column of a contact on the Contact tab, click Unverified to complete verification. Important Make sure that one or more contacts are created and added. Otherwise, alert notifications cannot be sent. For example, if you select DingTalk for the Notification parameter, a DingTalk chatbot must be added as a contact.
   	Notification object	The contacts to which alert notifications are sent. You can select multiple contacts. You can directly select or search for a contact. You must create contacts before you select contacts. To manage contacts, perform the following operations: Click Notification object management on the right side of Notification object. In the Edit Contact Group dialog box, click Edit in the Actions column on the Contact Group, Contact, Webhook, and DingTalk tabs separately, edit information, and then click Save. For more information about how to add a DingTalk chatbot and a webhook, see the FAQ section of this topic.

4. Click OK.

   After you create an alert rule, the rule is immediately effective. You can stop, edit, or delete the alert rule in the alert rule list.

ARMS

If a workspace uses ARMS to provide the monitoring and alerting service, you can subscribe to event-triggered alerts in the CloudMonitor console. You can subscribe to alerts only for the ECS failure handling events and ECS proactive O&M events. For more information about how to subscribe to alerts for deployment failures, see Development console of Realtime Compute for Apache Flink in the "Subscribe to event-triggered alerts" section of this topic. For more information about how to subscribe to other alerts, see CloudMonitor in the "Subscribe to event-triggered alerts" section of this topic.