Re: [Shinken-devel] How to access the configuration settings in a broker module
Status: Beta
Brought to you by:
naparuba
From: nap <nap...@gm...> - 2011-02-09 09:30:09
|
Hi, The bug was spotted and fixed (lastest git) :) And welcome on the THANKS file of the project ;) Jean On Wed, Feb 9, 2011 at 7:51 AM, nap <nap...@gm...> wrote: > Hi, > > Yes the modules are currently in refactoring pass. The properties[] things > were a so good idea to have Queue() or other things like it. Same for the > calling functions, we replace them by real "hook points", like how the > broker modules does. It will be simpler and a more powerful way for modules > to work :) > > For the customs variables yes, sounds like a bug, and I think I know where > it hide. The bug hunting is open, thanks for reporting :) > > > Jean > > >> >> 2011/2/8 Venelin Petkov <pet...@gm...> >> >> Hi, >>> >>> I finally came to the bottom of the problem. It turns out that it >>> may really be a shinken bug. Using your suggestion (BTW it does not >>> work on 0.5.1 since much of the module architecture has been changed) >>> I implemented the testing classes for my module and it worked! The >>> custom variable that is defined in the test configuration >>> (test/etc/1r_1h_1s/services.cfg) showed up, which left me baffled, >>> since I expected it to be faulty. Obviously it was a configuration >>> problem, so I systematically compared the test configuration with our >>> current Shinken configuration and found out that no custom variables >>> show up when the service definition contains only the 'hostgroup' >>> parameter, while services which have the 'host_name' parameter are >>> handled fine: >>> [...] >> >> >> >> > |