Fully managed Flink allows you to configure monitoring alerts for job running. If a monitoring rule is triggered during job running, the system sends you an alert message. This helps you detect and handle exceptions at the earliest opportunity. This topic describes how to configure Prometheus monitoring alerts in the Application Real-Time Monitoring Service (ARMS) console.


ARMS is activated. For more information, see Activate and upgrade ARMS.

Background information

When you configure monitoring alerts in ARMS, you must specify information, such as the cluster, type, dashboard, and Prometheus Query Language (PromQL). However, this method features complex operations, requires high learning costs, and delivers low efficiency for alert configuration. In the console of fully managed Flink, you can configure monitoring alerts. The console is easy to use and delivers high efficiency. For more information, see Configure monitoring alerts (in the console of fully managed Flink).


  1. Log on to the Realtime Compute for Apache Flink console.
  2. On the Fully Managed Flink tab, find the workspace that you want to manage, and click Console in the Actions column.
  3. In the left-side navigation pane, click Deployments.
  4. Click the name of the job for which you want to configure monitoring alerts.
    Note Select a job whose desired state and current state are both RUNNING.
  5. In the upper-right corner of the Overview page, click Metrics. Metrics
  6. In the left-side navigation pane, click Alerting. Alerting
  7. In the left-side navigation pane, choose Alerts > Alert Policies.
  8. In the upper-right corner of the page, choose Create Alarm > Prometheus. Prometheus
  9. In the Create Alarm dialog box, specify the parameters described in the following table. Relevant information
    Parameter Description
    Alarm Name Example: alert for network receiving pressure.
    Cluster Select the cluster for which you want to create the alert.
    Type Select grafana.
    Dashboard Select Flink.
    Chart Select a chart based on your business requirements.
    Alarm Rules Select Meet All of the Following Criteria.
    Last N Minutes Example: An alert is triggered if the value of N is 5 and the average value of bytes (MB) received by the network is greater than or equal to 3.
    Note A Grafana chart may contain multiple curves, such as A, B, and C. You can specify one of the curves to monitor as needed.
    PromQL Edit the PromQL statement or enter the PromQL statement again.
    Notice If the PromQL statement contains a dollar sign ( $), an error occurs. You must delete the parameters on both sides of the equal sign ( =) from the statement that contains the dollar sign ( $). For example, change sum (rate (container_network_receive_bytes_total{instance=~"^$HostIp.*"}[1m])) to sum (rate (container_network_receive_bytes_total[1m])).
    Notification Mode Select SMS, Email, or Ding Ding Robot.
    For more information about how to configure alerts for the DingTalk chatbot, see Configure a DingTalk chatbot to send alert notifications.
    Notice You must select Custom Keywords in the Security Settings section, and use keywords including Alarm. Otherwise, you cannot receive alert messages.
    Notification Receiver In the Contact Groups section, click the name of a contact group. If the contact group appears in the Selected Groups section, the setting succeeds.
  10. Click Save.