CDM Metrics
Function
Cloud Eye monitors the running status of cloud services and usage of each metric, and creates alarm rules for monitoring metrics.
After you create a CDM cluster, Cloud Eye automatically associates with CDM monitoring metrics to help you understand the running status of the CDM cluster.
- This section describes the CDM metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions.
- For details about CDM monitoring metrics, see Querying CDM Metrics.
- For details about how to set alarm rules, see Configuring CDM Alarm Rules.
Prerequisites
You have obtained required Cloud Eye permissions.
Namespace
SYS.CDM
Metrics
Table 1 lists the CDM metrics.
ID | Name | Description | Value Range | Unit | Conversion Rule | Dimension | Monitoring Period (Raw Data) |
|---|---|---|---|---|---|---|---|
bytes_in | Bytes In | Measures the network inbound rate of the monitored object. | ≥ 0 bytes/s | bytes/s | 1024(IEC) | instance_id | 1 minute |
bytes_out | Bytes Out | Measures the network outbound rate of the monitored object. | ≥ 0 bytes/s | bytes/s | 1024(IEC) | instance_id | 1 minute |
cpu_usage | CPU Usage | Measures the CPU usage of the monitored object. | 0% to 100% | % | N/A | instance_id | 1 minute |
mem_usage | Memory Usage | Measures the memory usage of the monitored object. | 0% to 100% | % | N/A | instance_id | 1 minute |
pg_pending_job | Number of Queued Jobs | Number of jobs in the PENDING state in the CDM instance. NOTE: This metric is available in version 2.10.0.300 and later versions. | >=0 | Count | N/A | instance_id | 1 minute |
pending_threads | Maximum Concurrent Extractors | Number of concurrent extraction threads in the Waiting state in the CDM instance. NOTE: This metric is available in version 2.10.0.300 and later versions. | >=0 | Count | N/A | instance_id | 1 minute |
disk_usage | Disk Usage | Measures the disk usage of the physical server accommodating the monitored ECS, which is not accurate as that obtained on the monitored ECS. | 0.001% to 90% | % | N/A | instance_id | 1 minute |
disk_io | Disk I/O | Measures the bytes read from and written to a disk per second on the physical server accommodating the monitored ECS, which is not accurate as those obtained on the monitored ECS. | ≥ 0 byte/s | byte/s | 1024(IEC) | instance_id | 1 minute |
tomcat_heap_usage | Heap Memory Usage | Measures the heap memory usage of the physical server accommodating the monitored ECS, which is not accurate as that obtained on the monitored ECS. | 0.001% to 90% | % | N/A | instance_id | 1 minute |
tomcat_connect | Tomcat Concurrent Connections | Measures the number of Tomcat concurrent connections on the physical server. | 0 to 2,147,483,647 | Count | N/A | instance_id | 1 minute |
tomcat_thread_count | Tomat Threads | Measures the number of Tomcat threads on the physical server. | 0 to 2,147,483,647 | Count | N/A | instance_id | 1 minute |
pg_connect | Database Connections | Measures the number of Postgres database connections on the physical server. | 0 to 2,147,483,647 | Count | N/A | instance_id | 1 minute |
pg_submission_row | Rows | Measures the number of rows in the submission table of the Postgres database on the physical server. | 0 to 2,147,483,647 | Count | N/A | instance_id | 1 minute |
pg_failed_job_rate | Job Failure Rate | Measures the job failure rate of the sqoop process on the physical server. | 0.001% to 100% | % | N/A | instance_id | 1 minute |
inodes_usage | Inodes Usage | Measures the disk inodes usage of the physical server accommodating the monitored ECS, which is not accurate as that obtained on the monitored ECS. | 0.001% to 100% | % | N/A | instance_id | 1 minute |
Dimension
Key | Value |
|---|---|
instance_id | CDM instance You can obtain the value by referring to "Querying a Specified Instance in a Cluster". |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.

