8 This check measures the throughput of block devices (disks) on Linux
9 hosts. You can either have a single check for every single disk
10 or a summary check (which is the default) summing up the throughput
13 For legacy reasons it is also possible (but not advisable) to have all disks
14 summarized but with a separate check for read and write (this is how this
15 check worked up to version 1.1.10).
17 The check also gives info on the IO latency and IOPS (unmerged) aquired
18 from the kernels information in /proc.
20 You can apply separate warning and critical levels for the read
21 and write throughput. Optionally you can have the check compute
22 average values on a configurable time period and have the levels
23 applied on the average instead of the current values. This makes
24 it possible to ignore short "peaks" and only trigger and longer
25 phases of high disk activity.
27 Averaging is not applied to IO latency calculations.
29 The check has to provide many ways of configuration for legacy reasons.
30 We strongly recommend you switch to the rule-based configuration, which
31 handles anything you want it to.
33 In single disk mode the check now also supports being used in a Check_MK
34 cluster environment. In this case it goes to CRIT if it finds more than
35 one disk item in the cluster. If it finds only one disk item, it also prints
36 the node name the disk was found on.
38 SUMMARY and legacy read/write modes are not supported in a cluster
39 configuration. The check goes to UNKNOWN and prints an appropriate message
40 if configured like that.
43 Either {"SUMMARY"} for a summarized check of all disks or the name of the
44 disk device, e.g. {"sda"}. Additionally also one service per logical volume
45 defined in Linux LVM and Veritas VxVM on Linux.
47 In order to support configurations
48 up to version 1.1.10 also the items {"read"} and {"write"} are supported.
52 The inventory is configured via {diskstat_inventory_mode}. If this is set
53 to {"single"} (the default), then one check will be created for each
54 disk. If it is set to {"summary"} then only one service per host will be
55 created that has at least one hard disk. If set to {"legacy"} then a
56 separate check for read and write will be created (deprecated).