Currently, only the overall zpool health status is published. It would be useful if the individual vdev and disk status were also published.
For example, this status
$ zpool status
...
config:
NAME STATE READ WRITE CKSUM
zpool1 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
wwn-0x5000c500b3b2f8c0 ONLINE 0 0 0
wwn-0x5000c500b3b53463 ONLINE 0 0 0
wwn-0x5000c500b3b33354 ONLINE 0 0 0
could lead to these metrics being published:
zfs_pool_health{pool="zpool1"} 0
zfs_pool_vdev_health{pool="zpool1", vdev="raidz1-0"} 0
zfs_pool_disk_health{pool="zpool1", vdev="raidz1-0" disk="wwn-0x5000c500b3b2f8c0"} 0
zfs_pool_disk_health{pool="zpool1", vdev="raidz1-0" disk="wwn-0x5000c500b3b53463"} 0
zfs_pool_disk_health{pool="zpool1", vdev="raidz1-0" disk="wwn-0x5000c500b3b33354"} 0
This would make it possible to build more informative dashboards. With only the pool health status, the operator still has to log into the server to find out which/how many devices are faulted.
Currently, only the overall zpool health status is published. It would be useful if the individual vdev and disk status were also published.
For example, this status
could lead to these metrics being published:
This would make it possible to build more informative dashboards. With only the pool health status, the operator still has to log into the server to find out which/how many devices are faulted.