Hi all,
I noticed I/O wait is added to total CPU usage and subtracted from CPU idle, in standard Zabbix metrics. iostat and sar manuals state I/O wait is, in fact, idle CPU. This seems to be the default behaviour across multiple Zabbix versions up to 7.
Is there a reason for that, or should...
2 results in 0.0023 seconds.
-
CPU metrics total usage and idle count I/O wait as usage, despite being idle
-
Problem with operations at auto registration
i've got a problem using an action at auto registration
I try to run a remote command (it enables a jmx interface for a host via the api) and add a template that uses a jmx interface but get the error "cannot find the JMX host interface" in the zabbix_server.log
...
