Maybe this is obvious but I am not finding where to do the following. I have Master and Slave sites. I have HOSTA being monitored on a Slave site. I have the Check Hosts with Ping rule enabled on the Master; however, since HOSTA is being monitored on the Slave (‘monitored from site’ setting on the host), that’s where the ping runs from.
How do I set up an active ping check from Master that also pings all the Slave-monitored nodes - not just the ‘monitored from site’ setting on the host itself?
I don’t see a “Monitored from Site” option in the Check Hosts with Ping ruleset – is there an equivalent workaround?
If I am understanding your question right, this should do it. Just curious, what’s the use case you’re trying to achieve here?
Create a host on your master site, Call it localhost.
Create a rule in the “Check hosts with ping”. Enter the slave monitored node name or IP address in the “'Alternative address to ping” field. Set the localhost as the explicit host parameter (at the bottom).
There might be another way, but as you say, it’s not obvious.
If you have hundreds of hosts to monitor this way, would be quicker to edit the rules.mk files directly.
Maybe this is obvious but I am not finding where to do the following. I have Master and Slave sites. I have HOSTA being monitored on a Slave site. I have the Check Hosts with Ping rule enabled on the Master; however, since HOSTA is being monitored on the Slave (‘monitored from site’ setting on the host), that’s where the ping runs from.
How do I set up an active ping check from Master that also pings all the Slave-monitored nodes - not just the ‘monitored from site’ setting on the host itself?
I don’t see a “Monitored from Site” option in the Check Hosts with Ping ruleset – is there an equivalent workaround?
Use case? The goal is to have my slave monitoring server (located in a cloud VPS environment [“the slave site”]) do the agent-level checks, but the master (located in my datacenter) do the active ping checks because a) if the Check_MK slave goes away, or the entire slave site becomes inaccessible from the network, I’ll only ever get an alert for the CMK slave being down and not its monitored hosts unless I have the master doing the ping checks, b) a latency check is more useful from the master remote site than locally to where the slave + its hosts are (where latency will always be in the microseconds). Scenario A occurred recently - all the hosts became inaccessible including the CMK slave server – and the only alerts received, as expected, were from the CMK slave being down, when I would have wanted all the hosts in the slave site to show up as ‘down’ hosts.
If I am understanding your question right, this should do it. Just curious, what’s the use case you’re trying to achieve here?
Create a host on your master site, Call it localhost.
Create a rule in the “Check hosts with ping”. Enter the slave monitored node name or IP address in the “'Alternative address to ping” field. Set the localhost as the explicit host parameter (at the bottom).
There might be another way, but as you say, it’s not obvious.
If you have hundreds of hosts to monitor this way, would be quicker to edit the rules.mk files directly.
Maybe this is obvious but I am not finding where to do the following. I have Master and Slave sites. I have HOSTA being monitored on a Slave site. I have the Check Hosts with Ping rule enabled on the Master; however, since HOSTA is being monitored on the Slave (‘monitored from site’ setting on the host), that’s where the ping runs from.
How do I set up an active ping check from Master that also pings all the Slave-monitored nodes - not just the ‘monitored from site’ setting on the host itself?
I don’t see a “Monitored from Site” option in the Check Hosts with Ping ruleset – is there an equivalent workaround?