← Back to team overview

nagios-charmers team mailing list archive

[Bug 1860669] [NEW] add support for enabling broker modules

 

Public bug reported:

Nagios has the ability to send send data to an event broker and we would
like to add support to the charm to be able to enable and configure
this. The docs have some important info about how best to do it at [1]
i.e.

Event Broker Options

Format: 	event_broker_options=<#>
Example: 	event_broker_options=-1

This option controls what (if any) data gets sent to the event broker
and, in turn, to any loaded event broker modules. This is an advanced
option. When in doubt, either broker nothing (if not using event broker
modules) or broker everything (if using event broker modules). Possible
values are shown below.

    0 = Broker nothing
    -1 = Broker everything
    # = See BROKER_* definitions in source code (include/broker.h) for other values that can be OR'ed together 

Event Broker Modules

Format: 	broker_module=<modulepath> [moduleargs]
Example: 	broker_module=/usr/local/nagios/bin/ndomod.o cfg_file=/usr/local/nagios/etc/ndomod.cfg

This directive is used to specify an event broker module that should by
loaded by Nagios at startup. Use multiple directives if you want to load
more than one module. Arguments that should be passed to the module at
startup are seperated from the module path by a space.

!!! WARNING !!!

Do NOT overwrite modules while they are being used by Nagios or Nagios
will crash in a fiery display of SEGFAULT glory. This is a
bug/limitation either in dlopen(), the kernel, and/or the filesystem.
And maybe Nagios...

The correct/safe way of updating a module is by using one of these
methods:

    Shutdown Nagios, replace the module file, restart Nagios
    While Nagios is running... delete the original module file, move the new module file into place, restart Nagios


[1]
https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/configmain.html

** Affects: nagios-charm
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1860669

Title:
  add support for enabling broker modules

Status in Nagios Charm:
  New

Bug description:
  Nagios has the ability to send send data to an event broker and we
  would like to add support to the charm to be able to enable and
  configure this. The docs have some important info about how best to do
  it at [1] i.e.

  Event Broker Options

  Format: 	event_broker_options=<#>
  Example: 	event_broker_options=-1

  This option controls what (if any) data gets sent to the event broker
  and, in turn, to any loaded event broker modules. This is an advanced
  option. When in doubt, either broker nothing (if not using event
  broker modules) or broker everything (if using event broker modules).
  Possible values are shown below.

      0 = Broker nothing
      -1 = Broker everything
      # = See BROKER_* definitions in source code (include/broker.h) for other values that can be OR'ed together 

  Event Broker Modules

  Format: 	broker_module=<modulepath> [moduleargs]
  Example: 	broker_module=/usr/local/nagios/bin/ndomod.o cfg_file=/usr/local/nagios/etc/ndomod.cfg

  This directive is used to specify an event broker module that should
  by loaded by Nagios at startup. Use multiple directives if you want to
  load more than one module. Arguments that should be passed to the
  module at startup are seperated from the module path by a space.

  !!! WARNING !!!

  Do NOT overwrite modules while they are being used by Nagios or Nagios
  will crash in a fiery display of SEGFAULT glory. This is a
  bug/limitation either in dlopen(), the kernel, and/or the filesystem.
  And maybe Nagios...

  The correct/safe way of updating a module is by using one of these
  methods:

      Shutdown Nagios, replace the module file, restart Nagios
      While Nagios is running... delete the original module file, move the new module file into place, restart Nagios


  [1]
  https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/configmain.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1860669/+subscriptions


Follow ups