Zabbix monitoring disk I/O

Zabbix_agentd.conf

Userparameter = custom. VFS. Dev. Read. Ops [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $4 }'

Userparameter = custom. VFS. Dev. Read. Ms [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $7 }'

Userparameter = custom. VFS. Dev. Write. Ops [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $8 }'

Userparameter = custom. VFS. Dev. Write. Ms [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $11 }'

Userparameter = custom. VFS. Dev. Io. Active [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $12 }'

Userparameter = custom. VFS. Dev. Io. Ms [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $13 }'

Userparameter = custom. VFS. Dev. Read. sectors [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $6 }'

Userparameter = custom. VFS. Dev. Write. sectors [*], CAT/proc/diskstats | grep $1 | head-1 | awk '{print $10 }'

Server

/Usr/local/zabbix/bin/zabbix_get-S x. x-P 10050-K Custom. VFS. Dev. Write. sectors [SDA]

The/proc/diskstats file contains three more domains than the/sys/block/HDC/STAT file, which correspond to the master device number, secondary device number, and device name from left to right. The subsequent 11 domains are the same in these two files, and their meanings will be explained below. All except the 9th domains are the cumulative values at startup.

1st domains: the number of disk reads and the total number of successful reads.

2nd fields: Number of merged reads and Field 6-Number of merged writes. For efficiency, adjacent reads and writes may be merged. Therefore, two 4 K reads may become an 8 K read before being processed to the disk. Therefore, only one I/O operation is performed. This domain allows you to know how frequently such operations are performed.

3rd domains: Number of read sectors, total number of successfully read sectors.

4th fields: the number of milliseconds consumed by reading, which is the number of milliseconds consumed by all read Operations (measured by _ make_request () to end_that_request_last ).

5th domains: the number of completed writes and the total number of successful writes.

7th domains: Number of write sectors, total number of successful write sectors.

8th fields: the number of milliseconds spent on writing. This is the number of milliseconds spent on all write operations (measured by _ make_request () to end_that_request_last ).

9th domains: the current progress of I/O. Only this domain should be 0. When a request is handed over to the appropriate request_queue_t, the addition and request Completion Time are reduced.

10th domains: the number of milliseconds spent on I/O operations. This domain will increase as long as field 9 is not 0.

11th domains: weighted, the number of milliseconds spent on I/O operations. This domain is added when I/O starts and I/O ends. This provides a convenient measurement standard for I/O completion time and storage that can be accumulated.

This article is from the "muzinan technology blog" blog, please be sure to keep this source http://muzinan110.blog.51cto.com/684213/1559792

Zabbix monitoring disk I/O