Hi to all,
We used Zabbix 1.8.14 previously and are now monitoring our ESXi infrastructure using Zabbix 2.0.2 and Zabbix Proxy 2.02 for remote site and Zabbix Java Gateway 2.0.2 for JMX.
I get many errors about "Disk I/O is overloaded" :
Trigger: Disk I/O is overloaded on drw-hudson-sup.mycorp.com
Trigger status: PROBLEM
Trigger severity: Warning
Trigger URL:
Item values:
1. CPU iowait time (drw-hudson-sup.mycorp.com:system.cpu.util[,iowait]): 25.29 %
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
And some time later, problem seems to be fixed :
Trigger: Disk I/O is overloaded on drw-hudson-sup.mycorp.com
Trigger status: OK
Trigger severity: Warning
Trigger URL:
Item values:
1. CPU iowait time (drw-hudson-sup.mycorp.com:system.cpu.util[,iowait]): 0.27 %
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
Latest data graph show there is such high cpu.iowait values
Did others get same behaviour ?
Some systems on our infra are still using Zabbix Agent 1.8.x and we see that some metrics, like free disk space reported as MB instead of GB, could be wrong.
What about cpu.iowait provided by Agents 1.8.x vs Agents 2.0 ?
Thanks all for your time
We used Zabbix 1.8.14 previously and are now monitoring our ESXi infrastructure using Zabbix 2.0.2 and Zabbix Proxy 2.02 for remote site and Zabbix Java Gateway 2.0.2 for JMX.
I get many errors about "Disk I/O is overloaded" :
Trigger: Disk I/O is overloaded on drw-hudson-sup.mycorp.com
Trigger status: PROBLEM
Trigger severity: Warning
Trigger URL:
Item values:
1. CPU iowait time (drw-hudson-sup.mycorp.com:system.cpu.util[,iowait]): 25.29 %
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
And some time later, problem seems to be fixed :
Trigger: Disk I/O is overloaded on drw-hudson-sup.mycorp.com
Trigger status: OK
Trigger severity: Warning
Trigger URL:
Item values:
1. CPU iowait time (drw-hudson-sup.mycorp.com:system.cpu.util[,iowait]): 0.27 %
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
Latest data graph show there is such high cpu.iowait values
Did others get same behaviour ?
Some systems on our infra are still using Zabbix Agent 1.8.x and we see that some metrics, like free disk space reported as MB instead of GB, could be wrong.
What about cpu.iowait provided by Agents 1.8.x vs Agents 2.0 ?
Thanks all for your time


Comment