Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Flexible and scalable monitoring framework
Python Shell Groff Ruby PHP Makefile Other
Failed to load latest commit information.
bin Fix: Create pid or run directory if missing. Context: Debian 8 remove…
cli Fix: (Arthur Lutz) manage void install call on CLI shinken install. Fix
contrib Fix connexion spelling to connection
doc Merge pull request #1653 from naparuba/shinken_notification
etc Don't activate by default the environments variable in shinken
external_commands Clean-up shell-scripts.
for_fedora add KillMode for all systemd daemon
inventory Renamed to .gitkeep
libexec Change: revert back to NO webui url by default
manpages Add shinken-discovery manpage and fix other manpages
modules Fix: missing test case for regression imported_from in the arbiter fo…
share Fix: get back the share directory so pack and modules can be installe…
shinken Fix: cpu looping for receiver
test Merge branch 'master' of https://github.com/naparuba/shinken
var Renamed to .gitkeep
.gitignore Fix tests
.pylintrc Enh: Pylintrc no report
.travis.yml Fix: some pep8 things
CONTRIBUTING.rst Enh : Add CONTRIBUTING file for PR
COPYING Change licence to AGPLv3. This must not so be important, but I don't …
Changelog Fix: (reported by David Guenault) SSL demo CA was limited to january …
FOR_PACKAGERS fix FOR_PACKAGERS
Governance.md Add: Governance to the project
MANIFEST.in Fix missing modules folder in the pip installation
README Rename README to README.rst and add a README symlink
README.rst Fix: missing badges in README
THANKS Add: Alexandre Viau to the THANKS file
clean.sh Add: move ini files into a etc/daemons directory.
requirements.txt Try to fix jenkins unit tests
setup.cfg Fix: get back the old setup.py until we fix new one for debian directly.
setup.py TAG: go 2.4

README.rst

Presentation of the Shinken project

Welcome to the Shinken project.

https://api.travis-ci.org/naparuba/shinken.svg?branch=master

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.

Requirements

See the Documentation

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

Installing Shinken

See the Documentation

Update

Launch:

python setup.py install --update

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

Running

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).
Something went wrong with that request. Please try again.