Original Message
Subject: [Nagios-users] event_broker_options and multiple broker modules
From: Wolfgang Powisch powo+lists.nagios-us...@powo.priv.at
To: Nagios List nagios-users@lists.sourceforge.net
Date: 2010-04-28 23:14
Hi,
I'm currently using NDOutils+MySQL to access both, live- and hitorical
data from Nagios-systems in a custom network management system.
Which Version of NDOUtils? If 1.4b7 I would not recommend it for
historical data, or in case, if you don't need correct data in
servicechecks, systemcommands and timedevents, you can keep it ;-)
Recently I noticed mk-livestatus and since the NDO-DB solution has
significant performance/scalability issues I'm planning to use
mk-livestatus for live-data-retrieval but keeping NDO for historical
data.
AFAIK mk-livestatus can also ask the core for historical data, but I
don't think parsing logs from the core would scale then. Also the
overall memory consumption of the core loading the mk-livestatus module
will will be more when having everything cached.
Basically it doesn't seem to be a problem to use both broker-modules
at the same time but I'd like to specify different
event_broker_options per broker_module. is that possible ?
On NDOUtils you can set the data processing options in ndomod.cfg - this
is just for the module itsself. Which event broker options are needed
for mk-livestatus - well that's the thing to ask the devs. Also there's
no option to set that directly onto the module as for it only gets the
live socket as param (and debug mode).
I would recommend that you ask on nagios-portal.org where the devs are
around.
Kind regards,
Michael
--
DI (FH) Michael Friedrich
michael.friedr...@univie.ac.at
Tel: +43 1 4277 14359
Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria
--
___
Nagios-users mailing list
Nagios-users@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
