Skip to content
This repository
Fetching contributors…

Cannot retrieve contributors at this time

file 27 lines (15 sloc) 1.496 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
== Fully compatible? ==

Not 100%, and it will never be. Some Nagios features are just useless in a Shiken architecture. For theses differences, you can look at the Shinken website:
http://www.shinken-monitoring.org/what-is-in-shinken-not-in-nagios-and-vice-versa/

== Do I need to change something? ==

No.

There are differences between some nagios parameters and the shinken way of doing things:
status_file and log_file parameters are no longer required in the nagios.cfg file for Shinken. External data interfaces are now managed as "modules" by the Brokers, and are in the shinken-specific.cfg file (look at Simple-log and Status-Dat modules, and put your paths on it).

Shinken will try to detect this and will autogenerate the modules for you. (But if you can move the configuration to the shinken-specific.cfg file, it's better...)


== Now, how do I launch Shinken with my nagios.cfg? ==

It's simple, after launching scheduler, poller, reactionner and broker daemons (see README), you just need
to launch the Arbiter daemon with your Nagios configuration:

$ /usr/local/shinken/src/shinken-arbiter.py -c /usr/local/nagios/etc/nagios.cfg -c /usr/local/shinken/src/etc/shinken-specific.cfg

(you can also be even more lazy and call the bin/launch_all.sh script).

And that's all :)

The Shinken arbiter can take multiple configuration files, so classic Nagios parameters are defined in nagios.cfg, all specific things (like daemons connections or realms) are in shinken-specific.cfg.
Something went wrong with that request. Please try again.