Hi!
Does anyone successfully use agent-checks together simple checks on one host?
If I mix simple checks like "ssh" or "ping" with agent checks, the availability of hosts that are unreachable becomes unstable. (This affects the special "status" item or the "available" column in the hosts table.)
The reason seems to be a bug in the logic, the zabbix-server calculates the availability of a host:
Since the only criteria for enabling a host seems to be the existence of at least one item that can be fetched, the simple check will cause the host availability to be set to HOST_AVAILABLE_TRUE, even if the check is negative (e.g. because the ping or ssh check failed to reach the host).
On the other hand, the agent checks will cause the availability to be set back to HOST_AVAILABLE_FALSE after CONFIG_UNREACHABLE_PERIOD.
This leads to continuous flapping of the host availability and thus the "status" item will also continuously flap.
Any workarounds for that? (Besides using only one type of checks. ;-))
Does anyone successfully use agent-checks together simple checks on one host?
If I mix simple checks like "ssh" or "ping" with agent checks, the availability of hosts that are unreachable becomes unstable. (This affects the special "status" item or the "available" column in the hosts table.)
The reason seems to be a bug in the logic, the zabbix-server calculates the availability of a host:
Since the only criteria for enabling a host seems to be the existence of at least one item that can be fetched, the simple check will cause the host availability to be set to HOST_AVAILABLE_TRUE, even if the check is negative (e.g. because the ping or ssh check failed to reach the host).
On the other hand, the agent checks will cause the availability to be set back to HOST_AVAILABLE_FALSE after CONFIG_UNREACHABLE_PERIOD.
This leads to continuous flapping of the host availability and thus the "status" item will also continuously flap.
Any workarounds for that? (Besides using only one type of checks. ;-))