Supported Metrics
Description
This section describes the DRS metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the DRS metrics and alarms.
Cloud Eye can monitor dimensions (or objects) nested to a maximum depth of four levels (levels 0 to 3). 3 is the deepest level. For example, if the monitored dimension of a metric is instance_id,node_id, instance_id indicates level 0 and node_id indicates level 1.
Namespace
SYS.DRS
DB Instance Monitoring Metrics
|
Metric ID |
Metrics Name |
Description |
Value Range |
Unit |
Conversion Rule |
Dimension |
Monitored Object |
Monitoring Interval (Raw Data) |
|---|---|---|---|---|---|---|---|---|
|
cpu_util |
CPU Usage |
CPU usage of the monitored object |
0-100 |
% |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
mem_util |
Memory Usage |
Memory usage of the monitored object |
0-100 |
% |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
network_incoming_bytes_rate |
Network Input Throughput |
Incoming traffic in bytes per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
network_outgoing_bytes_rate |
Network Output Throughput |
Outgoing traffic in bytes per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
disk_read_bytes_rate |
Disk Read Throughput |
Number of bytes read from the disk per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
disk_write_bytes_rate |
Disk Write Throughput |
Number of bytes written into the disk per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
disk_util |
Storage Space Usage |
Storage usage of the monitored object |
0-100 |
% |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
extract_bytes_rate |
Source Database Read Throughput |
Table data or WAL bytes read from the source database per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
extract_rows_rate |
Rows Read from Source Database per Second |
Number of table data or WAL rows read from the source database per second |
≥ 0 |
row/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
extract_latency |
Source Database WAL Extract Lag |
Latency of extracting WAL from the source database |
≥ 0 |
ms |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_bytes_rate |
Destination Database Write Throughput |
Number of bytes written into the destination database per second |
≥ 0 |
byte/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_rows_rate |
Rows Written into Destination Database per Second |
Number of rows written into the destination database per second |
≥ 0 |
row/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_transactions_rate |
DML TPS |
Number of DML transactions written into the destination database per second |
≥ 0 |
transaction/s |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_ddls_number or apply_ddls_rate
NOTE:
apply_ddls_rate is replaced by apply_ddls_number after December 2022. |
DDL TPS |
Total number of DDL transactions written into the destination database. |
≥ 0 |
transaction |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_latency |
Replication Delay |
Delay of data replay to the destination database |
≥ 0 |
ms |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_average_execute_time |
Average Transaction Execution Time |
Average execution time of a transaction in the destination database (RT = Execution time + Commit time) |
≥ 0 |
ms |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_average_commit_time |
Average Transaction Commit Time |
Average commit time of a transaction in the destination database (RT = Execution time + Commit time) |
≥ 0 |
ms |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_current_state |
Synchronization Status |
This metric is the synchronization status of the current kernel data (10: abnormal; 1: idle; 2: DML; 3: DDL), instead of the task status. |
10: abnormal 1: idle 2: DML is executed. 3: DDL is executed. |
N/A |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_thread_workers |
Synchronization Threads |
Number of working threads for data synchronization |
≥ 0 |
Counts |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
|
apply_job_status |
Task Status |
Status of the current task. (0: normal; 1: abnormal; 2: paused) |
0: normal 1: abnormal 2: paused |
N/A |
N/A |
instance_id |
Monitored object: ECS Monitored instance type: replication, synchronization, and DR instances |
1 minute |
If an object is in a hierarchical system, specify the monitored dimension in hierarchical form when you use an API to query the metrics of this object.
For example, if you want to query the disk usage (disk_util) of a DRS instance node, the dimension information of the metric is instance_id,node_id, indicating that instance_id is level 0 and node_id is level 1.
dim.0=instance_id,63d6c31c0ef94136b2a9aed0c6871b51in01&dim.1=node_id,371a239ba25c4bd0a4a5b1f54bb698a5no13
Dimensions
|
Key |
Value |
|---|---|
|
instance_id |
DRS instance ID |
|
node_id |
DRS node ID |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
