mod_bunny is a Nagios Event Broker (NEB) module that publishes host & service checks through a RabbitMQ AMQP broker, allowing you to distribute the checking load over multiple workers. It is similar to and heavily inspired from Mod-Gearman. The official worker implementation is bunny (written in Go).
mod_bunny relies on the following software:
Currently the installation method a little rough on the edges, since it needs the Nagios source tree to be compiled. The Nagios sources have to be "prepared" because the required config.h header is only available once the ./configure script has been successfully executed (no need to compile the sources). Once the sources are ready to be used, build the module as follows:
Note: you have to use the exact same sources version as the Nagios daemon binary.
NAGIOS_SOURCES=/usr/src/nagios-3.2.3 make
Once compiled, copy the binary module mod_bunny.o to Nagios's modules directory (usually /usr/lib/nagios3/modules).
In Nagios main configuration file (usually /etc/nagios3/nagios.cfg), add the following line (replace /usr/lib/nagios3/modules with the exact location of the compiled module on your system):
broker_module=/usr/lib/nagios3/modules/mod_bunny.o /etc/nagios3/mod_bunny.conf
Note: the parameter is the absolute path to mod_bunny's configuration file; not specifying this parameter will make mod_bunny only use its default settings, which will probably won't work for you. Also, if you use multiple broker modules, declare mod_bunny.o first as it needs to intercept some events early.
The configuration file is using JSON format. Here are the supported settings and their default value:
"host": "localhost"Broker hostname or address"port": 5672Broker port"vhost": "/"Broker virtual host"user": "guest"Broker account username"password": "guest"Broker account password"publisher_exchange": "nagios"Broker exchange to connect to for publishing checks messages"publisher_exchange_type": "direct"Broker publisher exchange type*"publisher_routing_key": "nagios_checks"Routing key to apply when publishing check messages"consumer_exchange": "nagios"Broker exchange to connect to for consuming checks result messages"consumer_exchange_type": "direct"Broker consumer exchange type"consumer_queue": "nagios_results"Queue to bind to for consuming check result messages"consumer_binding_key": "nagios_results"Binding key to use to consume check result messages"local_hostgroups": []Hostgroups** for which mod_bunny won't override checks (Nagios-local checks)"local_servicegroups": []Servicegroups** for which mod_bunny won't override checks (Nagios-local checks)"hostgroups_routing_table": {}Mapping of AMQP routing keys/hostgroups to use for dispatching host checks"servicegroups_routing_table": {}Mapping of AMQP routing keys/servicegroups to use for dispatching service checks"retry_wait_time": 3Time to wait (in seconds) before trying to reconnect to the broker"debug_level": 0Debugging level (0 = none, 1 = show Nagios events and AMQP events, 2 = same as 1 + dump received/sent AMQP messages)
* : To benefit from the round-robin load-balancing RabbitMQ feature, the publisher exchange MUST be of type direct. Read this to understand why.
** : local_hostgroups and local_servicegroups array elements are strings describing shell patterns, e.g. ["*-servers", "nagios_local"]
Basic configuration example:
{
"host": "some.amqp.broker.example.net",
"user": "bunny",
"password": "S3curEP4$$w0rd!"
}
Hostgroups/servicegroups routing table are useful for executing host/service checks by specific bunny workers:
{
...
"hostgroups_routing_table": {
"nagios_checks_oob": [ "oob", "net-*" ]
},
"servicegroups_routing_table": {
"nagios_checks_www": [ "www" ],
"nagios_checks_db": [ "mysql", "oracle", "postgresql" ]
}
}
In the configuration example above, all checks for hosts members of the hostgroup oob and all hostgroups matching the "net-*" wildcard will be published with the routing key "nagios_checks_oob": this way, only bunny workers bound to a queue matching this key will receive the checks. Similarily, all checks for services members of the servicegroup www will be executed by bunny workers bound to a queue matching the routing key "nagios_checks_www". All others host/checks will be published with the routing key defined by the publisher_routing_key setting.
mod_bunny has been tested with Nagios versions 3.2.3, 3.4.1 and 3.5.0 on Ubuntu Linux. Let me know if you successfully made it work on other platforms/versions.
Probably. The documentation related to NEB development is almost nonexistent, and the Nagios source code is a nightmare. I heavily relied on Mod-Gearman source code to understand how Nagios internals work, but I might have got or done some things wrong.
Currently mod_bunny only handles host/service checks events. I have no plans to support other events at the moment, but contributions are welcome.
This software is released under the MIT License.
Copyright (c) 2013 Marc Falzon / Cloudwatt
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.