Since you already had the master monitoring your hosts, if you only wanted them monitored on one or more slaves, you could go to 'WATO Configureation -> Hosts' and edit a host. In the 'Monitored on site' field, check the box then select which slave you want to monitor the host. When you activate the changes, both the host and slave configs will be updated. The host will be removed from the master and added to the slave. Rinse and repeat for any other hosts you want moved to slaves.
You *should* probably be able to do all of them at once by turning on the checkboxes and selecting the hosts, then clicking on 'edit', but that doesn't seem to work on my 1.2.4p5 version of Check_MK. I think I saw a fix for that in the 1.2.5* code... ----- Original Message ----- From: "Johnny Duane" <[email protected]> To: [email protected] Sent: Wednesday, August 13, 2014 4:30:47 PM Subject: Re: [omd-users] Duplicate host entries - Master Site monitoring hosts under Slave site? Thanks for the quick response guys! Jim, Just to clarify, i'm not actually configuring any hosts from the slave box? My understanding was that all configuration should be done on the master, and the settings would be pushed out to the slaves? If I tried to configure something on the slave machine, would the changes not be overwritten when I next updated the master? Is it not possible to add a host using wato on the master, but configure it to only be monitored by the slave? Tom, that was almost what I was looking for, but in reverse! I want the master to only see the monitoring results of these hosts through the slave's livestatus, but to be managed and configured by the master? Cheers again guys! John On 13 August 2014 21:12, Tom Moore < [email protected] > wrote: Actually, I just ran into the same thing yesterday. The solution is to go into your “Distributed Monitoring” section under WATO, edit your slave server, and tick the “Temporarily disable this connection” under the “Livestatus settings”. It just tells your master not to query the slave for its lists of hosts (because they will be the same).. useful in an active/active monitoring situation. Replication and everything else still works fine. Tom From: [email protected] [mailto: [email protected] ] On Behalf Of Jim Welch Sent: Wednesday, August 13, 2014 4:06 PM To: Johnny Duane Cc: [email protected] Subject: Re: [omd-users] Duplicate host entries - Master Site monitoring hosts under Slave site? It sounds like it's doing exactly what you told it to do. By importing the config to the master it started monitoring all the hosts, then you added specific hosts to the slaves so they also started monitoring them. If you don't want the master to monitor them, delete them from the master config. On my test setup, the only thing the master monitors directly are the slaves themselves. Just to see if I could, I added one of the hosts on a slave site to the master and it is now monitoring that host from both sites. --- From: "Johnny Duane" < [email protected] > To: [email protected] Sent: Wednesday, August 13, 2014 3:52:52 PM Subject: [omd-users] Duplicate host entries - Master Site monitoring hosts under Slave site? Hi all I'm not sure what to make of this? I have an OMD 1.10 multi-site/distributed environment that consists of 2 VM's (1 master and 1 slave) I've imported all the hosts that need to be monitored on the master, and placed a selection of them within a folder that has the setting "Monitored on site" set to my slave site/vm. Now when I click on the master's "all hosts" I can see the selected hosts listed under the slave site, titled "Monitor Slave 1". However, I also see them again still listed under the Master's site title "Monitor Master 1"? (ie the selected hosts are listed twice, one under each site title?) I would have expected the selected hosts to only be monitored and listed under the slave site/VM? I've also noticed that the data/graphs displayed by the duplicate entries are not the same as the originals, giving me the impression that both sites/vm's are in fact monitoring the same host? When I log directly onto the slave VM, I can see the wato config has been synced as it shows all the hosts and settings in the monitoring domain. However, when clicking on the slave's 'all hosts', only the hosts pre-selected on the master are shown being monitored, and nothing else. This is what i'd expect, but it also means the the site is obeying the configuration on what hosts it should be monitoring? I've searched high and low on-line, but cannot find any post that describes this scenario, making me think that this may actually be correct and there's a valid reason for it? Any help or advice you could give me on this would be really appreciated, even if its just to confirm whether this scenario is correct or not. Thanks! John _______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users _______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users _______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
