anyone sccesfully using the BP addon on Thruk talking to remote nagios host ?

[ibmnsb]

        we have multiple nagios hosts connected to Thruk. I have enabled the BP addon, but how would one go about setting up the BP addon so it can write to the /var/spool dir etc.

From what I understand this would be easier if Thruk and nagios were both installed locally. But what is Thruk is talking to say 10 different nagios hosts via livestatus. Is the Business process addon feasible in this  setup and if so please advise on how to go about it.

[Olivier]

Hi,
yes, me ! my thruk works with 2 remote nagios and 1 local nagios.
I give apache user to write on spool dir (drwxrwxr-x 2 nagios apache
/var/log/nagios/spool/checkresult)
The nagios services for thruk (/etc/nagios/thruk_bp_generated.cfg) work
on my local nagios

> --
> You received this message because you are subscribed to the Google
> Groups "Thruk" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to thruk+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[ibmnsb]

pardon my noobness, so i am trying to read the instruction here, http://www.thruk.org/documentation.html#_component_thruk_plugin_bp

from the configuration example below, is this setup on the thruk server locally ? and also looks like i can use "result_backend" to talk to my remote nagios using livestatus ? not sure if i got that right.

and the other three variables:

objects_save_file      = /etc/naemon/conf.d/bp_generated.cfg
objects_templates_file = /etc/naemon/conf.d/thruk_bp_templates.cfg
objects_reload_cmd     = /etc/init.d/naemon reload

are these files supposed to be present on the thruk macine locally ? I assume this example is for "naemon" whereas i will be using thruk.


Please advise




"Configuration Example:

<Component Thruk::Plugin::BP>

  #spool_dir             = /var/naemon/rw/check_results

  result_backend         = naemon

  objects_save_file      = /etc/naemon/conf.d/bp_generated.cfg

  objects_templates_file = /etc/naemon/conf.d/thruk_bp_templates.cfg

  objects_reload_cmd     = /etc/init.d/naemon reload

  #pre_obj_save_cmd      =

  #post_obj_save_cmd     =

  refresh_interval       = 1

</Component>"

[Sven Nierlein]

On 1/23/14 14:27, ibmnsb wrote:
> pardon my noobness, so i am trying to read the instruction here, http://www.thruk.org/documentation.html#_component_thruk_plugin_bp
>
> from the configuration example below, is this setup on the thruk server locally ? and also looks like i can use "result_backend" to talk to my remote nagios using livestatus ? not sure if i got that right.
>
> and the other three variables:
>
> objects_save_file = /etc/naemon/conf.d/bp_generated.cfg
> objects_templates_file = /etc/naemon/conf.d/thruk_bp_templates.cfg
> objects_reload_cmd = /etc/init.d/naemon reload
>
>
> are these files supposed to be present on the thruk macine locally ? I assume this example is for "naemon" whereas i will be using thruk.
>
>
> Please advise

Hi,

'result_backend' is something which is not released yet. This will be available with the next version. Naemon is a replacement for Nagios.
All files written by the BP engine are locally, yes. The idea is to have a local nagios, naemon, icinga, shinken core running which contains
all the business processes, even if they are based on remote sites.

Sven

[ibmnsb]

Thanks Sven,

               Firstly, thank you for your response and all the great work you keep doing to add more functionality to thruk.
 I checked the changelog after the post and I did see the 'result backend' will be available with the next release. Look forward to that.


OK, so here is my scenario, my thruk and nagios machines are all on separate machines, and as far as i understand all the config file will be on the thruk machine and with the next release i will be able to use 'result backend' and use livestatus (for remote nagios host) for the BP addon as well ?
So no write permission needed for the thruk host on the nagios machine, the only connection they will have is via livestatus. Hope i got that right.

[Sven Nierlein]

On 23.01.2014 14:53, ibmnsb wrote:
> Thanks Sven,
>
> Firstly, thank you for your response and all the great work you keep doing to add more functionality to thruk.
> I checked the changelog after the post and I did see the 'result backend' will be available with the next release. Look forward to that.
>
>
> OK, so here is my scenario, my thruk and nagios machines are all on separate machines, and as far as i understand all the config file will be on the thruk machine and with the next release i will be able to use 'result backend' and use livestatus (for remote nagios host) for the BP addon as well ?
> So no write permission needed for the thruk host on the nagios machine, the only connection they will have is via livestatus. Hope i got that right.

So completly. Livestatus will be used to submit the results from the BP engine and to restart the core if possible. But you cannot create or change
objects via Livestatus, so you still need access to the files. However, you could implement some kind of syncronisation with the pre/post_save_cmd hooks.

Sven