I'm surprised not to have seen this sooner: the devices reports seem to have disappeared on newer OS (Debian 11+12, rocky9). I think that I've found why: from sysstat 12.4.0, the DEV column is at the end of the report, and the code does not to seem to take this into account.
I'm wondering how to correct this.
[x] update pgcluu to swap the order of columns (in compute_srvtime_stat? I have already a headache)
[ ] update pgcluu_collectd not to add -p for sar >= 12.4.0 but I fear side effects on other reports like network...
# sar 10.1.5 (eg CentOS 7) ; DEV always at the beginning (-p or not)
# 12:14:34 DEV tps rd_sec/s wr_sec/s avgrq-sz avgqu-sz await svctm %util
# 12:14:34 vda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
# 12:14:34 vdb 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
# 12:14:34 vdc 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
# sar 11.7.3 (Rocky 8) sar 12.0.3 (Debian 10) ; DEV always at the beginning (-p or not)
# 12:03:57 DEV tps rkB/s wkB/s areq-sz aqu-sz await svctm %util
# 12:03:58 vda 1.00 0.00 4.00 4.00 0.02 28.00 24.00 2.40
#12:03:59 vda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
# sar 12.1.2 (compiled)
# 15:14:59 DEV tps rkB/s wkB/s dkB/s areq-sz aqu-sz await %util
# 15:15:00 nvme0n1 6.00 0.00 40.00 0.00 6.67 0.04 6.83 1.60
# sar 12.4.0 (compiled) ; DEV at the end if -p (pretty)
# 15:18:38 tps rkB/s wkB/s dkB/s areq-sz aqu-sz await %util DEV
# 15:18:39 3.00 0.00 40.00 0.00 13.33 0.01 3.67 1.20 nvme0n1
# 15:18:39 11.00 0.00 40.00 0.00 3.64 0.07 6.55 1.20 nvme0n1p3_crypt
# sar 12.5.2 (Ubuntu 22.04, Debian 11) , 12.5.4 (Rocky 9), 12.6.1 (Debian 12)
# 14:07:06 tps rkB/s wkB/s dkB/s areq-sz aqu-sz await %util DEV
# 14:07:07 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 nvme0n1
# 14:07:07 0,00 0,00 0,00 0,00 0,00 0,00 0,00 0,00 nvme0n1p3_crypt
I'm surprised not to have seen this sooner: the devices reports seem to have disappeared on newer OS (Debian 11+12, rocky9). I think that I've found why: from sysstat 12.4.0, the DEV column is at the end of the report, and the code does not to seem to take this into account. I'm wondering how to correct this.
compute_srvtime_stat
? I have already a headache)-p
for sar >= 12.4.0 but I fear side effects on other reports like network...