Monitored Metrics
Description
After installing the Agent on a BMS, you can view its OS monitoring metrics. Monitoring data is collected at an interval of 1 minute.
Namespace
SERVICE.BMS
Metrics
Table 1 lists the metrics supported by BMS.
Metric ID |
Metric |
Description |
Value Range |
Monitored Object |
Monitoring Interval (Raw Data) |
---|---|---|---|---|---|
cpu_usage |
(Agent) CPU Usage |
CPU usage of the monitored object Obtain its value by checking metric value changes in the /proc/stat file in a collection period. Run the top command to check the %Cpu(s) value. Unit: percent |
0-100% |
BMS |
1 minute |
load_average5 |
(Agent) 5-Minute Load Average |
CPU load averaged from the last 5 minutes Obtain its value by dividing the load5/ value in /proc/loadavg by the number of logical CPUs. Run the top command to check the load5 value in the /proc/loadavg file. |
≥ 0 |
BMS |
1 minute |
mem_usedPercent |
(Agent) Memory Usage |
Memory usage of the monitored object Obtain its value by checking the file /proc/meminfo. Memory Usage = (MemTotal - MemAvailable)/MemTotal Unit: percent |
0-100% |
BMS |
1 minute |
mountPointPrefix_disk_free |
(Agent) Available Disk Space |
Available disk space of the monitored object Run the df -h command to check the data in the Avail column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~). Unit: GB |
≥ 0 GB |
BMS |
1 minute |
mountPointPrefix_disk_usedPercent |
(Agent) Disk Usage |
Disk usage of the monitored object. It is calculated as follows: Disk Usage = Used Disk Space/Disk Storage Capacity. Disk Usage = Used Disk Space/Disk Storage Capacity The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~). Unit: percent |
0-100% |
BMS |
1 minute |
mountPointPrefix_disk_ioUtils and volumePrefix_disk_ioUtils |
(Agent) Disk I/O Usage |
Disk I/O usage of the monitored object Obtain its value by checking data changes in the thirteenth column of the corresponding device in the /proc/diskstats file in a collection period. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~). Unit: percent |
0-100% |
BMS |
1 minute |
mountPointPrefix_disk_inodesUsedPercent |
(Agent) Percentage of Total inode Used |
Percentage of used index nodes on the disk Run the df -i command to check data in the IUse% column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), dots (.), and swung dashes (~). Unit: percent |
0-100% |
BMS |
1 minute |
net_bitRecv |
(Agent) Inbound Bandwidth |
Number of bits received by this NIC per second Check metric value changes in the /proc/net/dev file in a collection period. Unit: bit/s |
≥ 0 bit/s |
BMS |
1 minute |
net_bitSent |
(Agent) Outbound Bandwidth |
Number of bits sent by this NIC per second Check metric value changes in the /proc/net/dev file in a collection period. Unit: bit/s |
≥ 0 bit/s |
BMS |
1 minute |
net_packetRecv |
(Agent) NIC Packet Receive Rate |
Number of packets received by this NIC per second Check metric value changes in the /proc/net/dev file in a collection period. Unit: count/s |
≥ 0 counts/s |
BMS |
1 minute |
net_packetSent |
(Agent) NIC Packet Send Rate |
Number of packets sent by this NIC per second Check metric value changes in the /proc/net/dev file in a collection period. Unit: count/s |
≥ 0 counts/s |
BMS |
1 minute |
net_tcp_total |
(Agent) TCP TOTAL |
Total number of TCP connections of this NIC |
≥0 |
BMS |
1 minute |
net_tcp_established |
(Agent) TCP ESTABLISHED |
Number of ESTABLISHED TCP connections of this NIC |
≥0 |
BMS |
1 minute |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.