Re: [Nagios-devel] configuration directory

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] configuration directory

Post by Guest »

> On 2013-09-04 00:34, AL13N wrote:
>> Op dinsdag 3 september 2013 17:22:32 schreef Andreas Ericsson:
>>> On 2013-09-02 21:20, AL13N wrote:
>>>> Hi,
>>>>
>>>> i'm a Mageia distribution packager, and i'm maintaining some event
>>>> broker
>>>> modules.
>>>>
>>>> since these are packaged seperately we're trying to get things to wo=
rk
>>>> out-of- the-box for our users, specifically adding event brokers in
>>>> the
>>>> configuration file for nagios.
>>>>
>>>> the problem we're facing is that: We don't want a nagios addon packa=
ge
>>>> to
>>>> rewrite the configuration file itself. however, we would like to add
>>>> the
>>>> event broker (or other settings) and then reload/restart nagios.
>>>>
>>>> a beneficial thing would be a configuration directory (much like it
>>>> exists
>>>> with hosts and commands and stuff like that) but for the main nagios
>>>> configuration file.
>>>>
>>>> and if while we're at it, to have multiple directories, where
>>>> /usr/share/nagios/nagios.d/ has the "defaults" which can be overridd=
en
>>>> in
>>>> /etc/nagios.d/ (for instance) (this is a convention that's growing i=
n
>>>> use)
>>>>
>>>> I can try to start making a patch for this, but i'm asking about thi=
s
>>>> first, in order to find out if it makes a chance of getting accepted=
.
>>>
>>> Not only does it stand a chance of getting accepted; It's on the
>>> roadmap. If you start working on it I'll help as much as I can and
>>> I'm willing to accept less-than-awesome quality code, although I'll
>>> polish such later if it turns out to be an issue.
>>>
>>> The only real requirement is that any "main" config file option
>>> should be settable from any file in the dropdir.
>>
>>
>> the idea i thought might be doable, would be to allow multiple -d
>> options to
>> nagios, and allow those to be a file or a directory.
>>
>
> I'd much rather see this as "include=3D/some/path.d" where we read all
> files ending with .cfg and .conf if it's a directory, or the file if
> it's a fail, and then parse each include'd file in order of
> include-statement -> lexicographical order
> so that
>
> include=3D/etc/nagios.conf.d/
> include=3D/etc/nagios.perfdata.d/
>
> would cause all files from /etc/nagios.conf.d to be parsed before all
> files from /etc/nagios.perfdata.d.
>
> The included files can include other files, if they're so inclined.

so, you mean to keep one nagios.cfg file and have include=3D/path/to/foo.

would this mean that if you have

setting1=3Dvalue

setting2=3Dvalue

include=3D/path/to/foo

setting3=3Dvalue

that being parsed would:
1) setting1
2) setting2
3) all from /path/to/foo if it's a file or directory
4) setting3


is this the priority that you aim for?






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: alien@rmail.be
Locked