Flexible and scalable monitoring framework
Python Shell Roff Ruby PHP Makefile Other
Failed to load latest commit information.
bin Fix: TEST should fix fedora installation tests, but alpine will be a … Oct 2, 2017
cli Add support of proxy socks5 for shinken cli (#1583) Apr 30, 2016
contrib Fix connexion spelling to connection Mar 5, 2015
doc Add instructions to use --install-scripts in pip (#1890) Sep 19, 2017
etc Merge remote-tracking branch 'upstream/master' into enh_mem_leak_hunting May 4, 2017
external_commands Clean-up shell-scripts. Jul 16, 2012
for_fedora Improve systemd units reliability May 5, 2016
inventory Renamed to .gitkeep Nov 26, 2014
libexec Fix osmatch in nmap discovery process (#1944) Mar 14, 2018
manpages Typo: Update some doc files. (#1821) Apr 30, 2016
modules Fix: missing test case for regression imported_from in the arbiter fo… Apr 30, 2015
share Fix: get back the share directory so pack and modules can be installe… Dec 17, 2014
shinken CherryPy >= 3 required (#1943) Mar 14, 2018
solaris/smf add solaris SMF manifests May 28, 2015
test Fix: TEST on "old"debian6 releases Mar 14, 2018
var Renamed to .gitkeep Nov 26, 2014
.gitignore Added some more git ignored patterns Aug 28, 2015
.pylintrc Enh: Pylintrc no report Jan 26, 2015
.travis.yml Enh: Backport test suite from OpsBro to test installations in various… Oct 2, 2017
CONTRIBUTING.rst Enh : Add CONTRIBUTING file for PR Jul 18, 2014
COPYING Change licence to AGPLv3. This must not so be important, but I don't … Jul 15, 2009
Changelog Add: Update Changelog with last fixes/backport from Enterprise version. Mar 1, 2017
Governance.md Add: Governance to the project Feb 11, 2015
MANIFEST.in Fix missing modules folder in the pip installation Apr 17, 2014
README Rename README to README.rst and add a README symlink Apr 11, 2011
README.rst Fix: missing badges in README May 29, 2015
THANKS Add: Alexandre Viau to the THANKS file Jun 27, 2014
clean.sh Add: move ini files into a etc/daemons directory. Jul 11, 2013
requirements.txt CherryPy >= 3 required (#1943) Mar 14, 2018
setup.cfg Fix: get back the old setup.py until we fix new one for debian directly. Apr 13, 2015
setup.py Fix: installation with pip and local file. Oct 2, 2017


Presentation of the Shinken project

Welcome to the Shinken project.


Shinken is a modern, Nagios compatible monitoring framework, written in Python. Its main goal is to give users a flexible architecture for their monitoring system that is designed to scale to large environments.

Shinken is backwards-compatible with the Nagios configuration standard and plugins. It works on any operating system and architecture that supports Python, which includes Windows, GNU/Linux and FreeBSD.


See the Documentation

There are mandatory and conditional requirements for the installation methods which are described below.

Installing Shinken

See the Documentation



python setup.py install --update

It will only update the shinken lib and scripts, but won't touch your current configuration


Shinken is installed with init.d scripts, enables them at boot time and starts them right after the install process ends. Based on your linux distro you only need to do:

chkconfig --add shinken chkconfig shinken on

or :

update-rc.d shinken defaults 20

Where is the configuration?

The configuration is on the directory, /etc/shinken.

Where are the logs?

Logs are in /var/log/shinken (what did you expect?)

I got a bug, how to launch the daemons in debug mode?

You only need to launch:

/etc/init.d/shinken -d start

Debug logs will be based on the log directory (/var/log/shinken)

I switched from Nagios, do I need to change my existing Nagios configuration?

No, there is no need to change the existing configuration - unless you want to add some new hosts and services. Once you are comfortable with Shinken you can start to use its unique and powerful features.

Learn more about how to use and configure Shinken

Jump to the Shinken documentation.

If you find a bug

Bugs are tracked in the issue list on GitHub . Always search for existing issues before filing a new one (use the search field at the top of the page). When filing a new bug, please remember to include:

  • A helpful title - use descriptive keywords in the title and body so others can find your bug (avoiding duplicates).
  • Steps to reproduce the problem, with actual vs. expected results
  • Shinken version (or if you're pulling directly from the Git repo, your current commit SHA - use git rev-parse HEAD)
  • OS version
  • If the problem happens with specific code, link to test files (gist.github.com is a great place to upload code).
  • Screenshots are very helpful if you're seeing an error message or a UI display problem. (Just drag an image into the issue description field to include it).