Autodiscovery does not activate changes when host check command is set to "Use the status of the Check_MK Agent"

Troubleshooting
1

Hello
i just discovered that if the Host check command is set to “Use the status of the Check_MK Agent”, the Service discovery won’t activate changes. It’ll find the services defined by the rules but hangs at “rediscovery scheduled”.
I found this accidentally with our new instance in the GCP where i had to set this rule first because ICMP didn’t work.
1.6p17CEE

BR Thomas

2

Yes, I’ve noticed that as well. In my case the problem is: if the status of the Check_MK Agent goes WARN or CRIT, then the host itself is considered DOWN. And the automatic service discovery skips hosts that are DOWN, so it won’t auto repair itself in this situation by doing a discovery that resets the state of the Agent back to OK.

3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.