Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-09 Thread Venelin Petkov
Hi, I wanted to confirm that everything works all right now. Thanks for your support! Venelin On Wed, Feb 9, 2011 at 10:30 AM, nap wrote: > 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, n

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-09 Thread nap
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 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 i

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-08 Thread nap
t;> > class TestConfigSmall(TestConfig): >> >def setUp(self): >> >self.setup_with_file('etc/nagios_1r_1h_1s.cfg') >> >self.livestatus_broker = Livestatus_broker(modconf, >> > your_own_params.) >> >self.livest

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-08 Thread Grégory Starck
lf.setup_with_file('etc/nagios_1r_1h_1s.cfg') > >self.livestatus_broker = Livestatus_broker(modconf, > > your_own_params.) > >self.livestatus_broker.create_queues() > > self.livestatus_broker.init() > > self.sched.fill_initial_br

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-08 Thread Venelin Petkov
broker() > > > and then the test_venelin from above > > > Change all the livestatus stuff with your own module's name. The > update_broker() routine puts broks to the broker module and calls all the > manage_* methods. > > > Gerhard > > > > >

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-07 Thread Gerhard Lausser
he manage_* methods. Gerhard > -Ursprüngliche Nachricht- > Von: Venelin Petkov [mailto:petkov.vene...@gmail.com] > Gesendet: Montag, 7. Februar 2011 09:31 > An: shinken-devel@lists.sourceforge.net > Betreff: Re: [Shinken-devel] How to access the configuration > settings in a b

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-07 Thread Venelin Petkov
Hi Gerhard, Here is exactly what I am doing: Excerpt from the conf (I defined custom variables for all 9 services in this test configuration, just to be sure): define service{ use local-service hostgroup_name print service_des

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Gerhard Lausser
> need, but somehow the custom variable that I have defined in > each service, namely _udp_template, does not appear in So if you fill a sevice-dict like in livestatus_broker.py and then look at the elements for svc in service-list.values(): print "list of customs", get_customs_keys(svc.c

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Venelin Petkov
Hi Jean, We decided to try out your suggestion (we may later on make an arbiter module), so I looked into LiveStatus and it seems exactly what we needed. By implementing manage_initial_service_status_brok(self, b) I am getting all the information about the services that I need, but someho

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Hermann Lauer
On Fri, Feb 04, 2011 at 12:56:30PM +0100, nap wrote: > > Why not as an arbiter module? It can receive such things after all. Nice idea, as the server is rather simple. It only needs to sit on the host with the rrd files. > On Fri, Feb 4, 2011 at 12:49 PM, Flyinvap wrote: > > > Hi, > > > > Le 0

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Flyinvap
> Which kind of protocol and server do you use ? I think shinken (or > nagios) can talk with collectd [0] with collectd'd network binary > protocol [1]. It could be a great solution for manager perfdata. > Better with [0] http://collectd.org/ [1] http://collectd.org/wiki/index.php/Binary_prot

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread nap
Hi, Why not as an arbiter module? It can receive such things after all. Jean On Fri, Feb 4, 2011 at 12:49 PM, Flyinvap wrote: > Hi, > > Le 04/02/2011 10:38, Venelin Petkov a écrit : > > I am developing two simple shinken modules, based on > > host_perfdata_broker and service_perfdata_broker,

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread nap
On Fri, Feb 4, 2011 at 12:03 PM, Hermann Lauer < hermann.la...@iwr.uni-heidelberg.de> wrote: > Hello Jean, > Hi, > > On Fri, Feb 04, 2011 at 10:52:19AM +0100, nap wrote: > > On Fri, Feb 4, 2011 at 10:38 AM, Venelin Petkov < > petkov.vene...@gmail.com>wrote: > > > But just parsing the perfdata is

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Flyinvap
Hi, Le 04/02/2011 10:38, Venelin Petkov a écrit : > I am developing two simple shinken modules, based on > host_perfdata_broker and service_perfdata_broker, that send udp > packets containing performance data to a logging server, which in turn > stores them in rrd databases Which kind of proto

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread Hermann Lauer
Hello Jean, On Fri, Feb 04, 2011 at 10:52:19AM +0100, nap wrote: > On Fri, Feb 4, 2011 at 10:38 AM, Venelin Petkov > wrote: > > But just parsing the perfdata isn't good enough? The format is quite > standard (http://nagios.sourceforge.net/docs/3_0/perfdata.html). writing a parser and all the cor

Re: [Shinken-devel] How to access the configuration settings in a broker module

2011-02-04 Thread nap
On Fri, Feb 4, 2011 at 10:38 AM, Venelin Petkov wrote: > Hello all, > > Hi, > I am developing two simple shinken modules, based on > host_perfdata_broker and service_perfdata_broker, that send udp > packets containing performance data to a logging server, which in turn > stores them in rrd dat