Updated on 2025-01-21 GMT+08:00

Viewing Monitoring Metrics

Scenario

After you start a real-time migration job, Cloud Eye automatically associates monitoring metrics of the job. This helps you learn the status of the job.

It takes some time for the system to obtain and transmit monitoring data, so the job status displayed on the Job Monitoring page is not up-to-date. If you just started a real-time migration job, wait for 5 to 10 minutes and then view the monitoring data.

Prerequisites

  • You have obtained required Cloud Eye permissions.
  • The real-time migration job is running properly. If it has been stopped or is abnormal, you can only view its monitoring metrics in the last seven days.
  • The real-time migration job has been running properly for about 10 minutes.

Supported Monitoring Metrics

Table 1 lists the monitoring metrics supported for real-time processing migration jobs.

Table 1 Monitoring metrics supported for real-time processing migration jobs

Metric Name

Description

Value Range

Monitored Object

Monitoring Period (Raw Data)

Source Database WAL Extraction Latency

Latency of extracting WALs from the source database

≥ 0 ms

Real-time processing migration job

1 minute

Job Data Read Rate

Data input rate of a Flink job for monitoring and debugging

≥ record/s

Real-time processing migration job

1 minute

Job Data Write Rate

Data output rate of a Flink job for monitoring and debugging

≥ record/s

Real-time processing migration job

1 minute

Job Total Data Read

Total number of data inputs of a Flink job for monitoring and debugging

≥ records

Real-time processing migration job

1 minute

Job Total Data Write

Total number of output data records of Flink jobs for monitoring and debugging.

≥ records

Real-time processing migration job

1 minute

Job Byte Read Rate

Input bytes of a Flink job per second

≥ Byte/s

Real-time processing migration job

1 minute

Job Byte Write Rate

Output bytes of a Flink job per second

≥ Byte/s

Real-time processing migration job

1 minute

Job Total Read Byte

Total number of input bytes of a Flink job

≥ Byte/s

Real-time processing migration job

1 minute

Job Total Write Byte

Total number of output bytes of a Flink job

≥ Byte/s

Real-time processing migration job

1 minute

Job CPU Usage

CPU usage of the Flink job

≥ 0%

Real-time processing migration job

1 minute

Job Memory Usage

Memory usage of the Flink job

≥ 0%

Real-time processing migration job

1 minute

Job Maximum Operator Latency

Maximum operator latency of a Flink job, in milliseconds

≥ 0 ms

Real-time processing migration job

1 minute

Job Maximum Operator Backpressure

Maximum operator back pressure value of a Flink job. The value ranges from 0 to 1. A larger value indicates severer back pressure.

≥ 0

Real-time processing migration job

1 minute

Procedure

  1. Log in to the DataArts Studio console by following the instructions in Accessing the DataArts Studio Instance Console.
  2. On the DataArts Studio console, locate a workspace and click DataArts Factory.
  3. In the left navigation pane of DataArts Factory, choose Monitoring > Job Monitoring.
  4. On the Real-Time Migration Jobs page, click a job name.
    Figure 1 Monitoring a real-time migration job
  5. On the details page, click the Monitoring Information tab. You can view some key metrics of the job at the bottom of the page.
    Figure 2 Key metrics
  6. Click View Monitoring Metrics to go to the Cloud Eye console and view monitoring metrics.
    Figure 3 Viewing monitoring metrics

    For more information about monitoring metrics, see the Cloud Eye User Guide.