active_checks_enabled per service

Support requests, bug reports, questions etc.
Locked
benny

active_checks_enabled per service

Post by benny » Mon Nov 16, 2009 22:56

Hey folks,

I'm working on adding some Windows EventLog checks to my hosts, and I ran into a strangeness with NConf... With the Windows EventLog Agent I'm using, I need to set services to be passive only, no active checks. So, I start walking my way through NConf, to see where active_checks_enabled and passive_checks_enabled are set...

I found them in the Nagios Collectors category. But, this is a setting that can be *MUCH* more finer-grained than that, and I need to take it down to the service level.

SO. I'm pretty sure I can change this to operate like I would like - I can remove these two tokens from the nagios-collector's attribute list, and add them to services. What I'm asking is whether or not this will cause any issues? I know messing with the attributes is cautioned against, but I'm finding a lot of these and I'm curious to know if the rest of you are meddling with them as much as I am. :)

Thanks everyone!

Benny

User avatar
agargiulo
NConf developer
NConf developer
Posts: 725
Joined: Fri Mar 06, 2009 17:50
Location: Zurich, Switzerland
Contact:

Re: active_checks_enabled per service

Post by agargiulo » Tue Nov 17, 2009 10:19

Hi.

Long answer:
In NConf 1.2.5 this will cause big issues, because it would mess up the distributed monitoring concept of NConf.
In NConf 1.2.6 however, we have added Nagios-style host- & service-templates, which can be assigned individually to each host or service. You will still be able to set options on a global level (such as the collector options), but you will be able to override them for each host or service individually.

Short answer:
Wait for NConf 1.2.6 which is to be released this week...

benny

Re: active_checks_enabled per service

Post by benny » Tue Nov 17, 2009 14:58

How excellent. :) I was hoping that would be changed in this next release.

Thanks a bunch!

Benny

Locked