Just posting my thoughts really, and any input would be appreciated.
Here is my brain dump.....
I currently use nagios core to monitor multiple sites globally, and am in the process of distributing this using NSCA.
The idea is, currently I use nagios to monitor a very specific application server stack, and that one benefit of distributing this to local IT would allow (as well as the reduced load on the Central Nagios server), the local IT teams to extend my foundation NAGIOS configuration to monitor there other IT Systems.
I am considering using, source control to ensure that configurations are kept consistent, where by the Local NAGIOS server could perform a nightly SVN update to get any new cfg files, plugins. Then Reload nagios.
I have a basic .cfg file structure that allows me to distribute my core configuration, however I can see issue arrising if local IT staff edit the nagios.cfg to include their extended configuration (That I do not care about - I will provide a template that will ensure Obsess over services and hosts for their extension configs, is disabled)
My thoughts are:
If I created a dir within each site called Local, in which I could include a nagiosLocal.cfg which could look something like this;
Code: Select all
cfg_dir=/etc/nagios/local/commands
cfg_dir=/etc/nagios/local/services
cfg_dir=/etc/nagios/local/hosts
Does anyone have any insight in to this... at the moment this is just my thoughts, I am open to suggestions on improving this idea.
Mitchell