You might also have to set the uncommitted column to 1 for each host in question so Opsview will know the config has changed. I'm not sure if Opsview selectively build's configs based on the uncommitted column but it must be there for a reason.
Anytime I've done mass changes to hosts at the database level I've done it but can't remember if it is required? If you are just moving all hosts to a monitoring server it should be pretty easy, otherwise you will have to match on a pattern or patterns as Rafael suggested.. James Whittington VC3, Inc. From: [email protected] [mailto:[email protected]] On Behalf Of Rafael Carneiro Sent: Monday, February 01, 2010 2:51 PM To: Opsview Users Subject: Re: [opsview-users] move hosts to slave If your hostnames have a pattern, this may help: UPDATE opsview.hosts SET monitored_by = 6 WHERE name LIKE 'PHX%' (don't forget to replace 6 with the id for your slave) This is not supported/recommended, so make sure that you either know what you're doing or backup your opsview DB before doing this. Rafael On Mon, Feb 1, 2010 at 2:35 PM, Ryan Goldberg <[email protected]<mailto:[email protected]>> wrote: Just wondering if there's anything more I need to do aside from updating the "monitored_by" in the "hosts" table to the correct value in order to move them around. I have to update about 1000 hosts, and doing it by hand, hmm, painful... Ryan _______________________________________________ Opsview-users mailing list [email protected]<mailto:[email protected]> http://lists.opsview.org/lists/listinfo/opsview-users
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
