auditing Nagios configs

Roger Roger at NagiosWiki.com
Wed Feb 27 17:16:48 CET 2008


On 2/26/08, Mark L Potter <mark.potter at academy.com> wrote:
>
>
> On Mon, 2008-02-25 at 16:20 -0800, Roger wrote:
> > Does anyone have any tools or tips on auditing Nagios configs when
> > you're consolidating boxes?
> >
> >
> I would be pretty easy to do with a little sed and awk or grep and cut
> script. If you want to describe your config a little more I might could
> throw something together for you. I would need to know if you are using
> single file configs or if you are using multiple files and if those
> files are all in the same dir and so on. I think it would be under 20
> lines total to get what you want.



So, for example, say ou have servers 1, 2, 3. And they have services ABC,
ABXYZ, and AWC respectively.

Say I know server 1 and 3 should be the same in terms of service checks, so
now I have to go and add services B to server 3 and service W to server 1 so
that they both have ABCW as services.  Right now, I'm doing all of this
manually, and am looking for quick(er) ways to do so.

Many environments grow organically and people just slam in checks without
thinking about what other servers might need that same check, and then at
the end of the day when one person has to make sense of it all, manually
sifting through everything can get time consuming.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080227/9d175441/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null


More information about the Users mailing list