### UI

[![Shinken UI](https://github.com/shinken-monitoring/mod-webui/raw/master/doc/animation.gif)](https://www.shinken-enterprise.com/en/product/)

[Shinken WebUI](https://github.com/shinken-monitoring/mod-webui/wiki) is proven itself to work well with thousands of hosts and tens of groups.

### Drawbacks

I found no visible drawbacks, based on the documentation. The only thing that concerns me is its rapid development in the past and [very slow pace of commits](https://github.com/naparuba/shinken/commits/master) in the present: around 40 commits this year; most are pull requests merged, so no new development is going on, and only community-written bugfixes are being included. It’s either too good to move on (which is never the case; even old-timers like vim and emacs get their code updated) or it’s another opensource project that not enough people care about — you should know such things before using such a complex thing as a monitoring system.

[Frédéric Mohier](https://github.com/mohierf) was very kind to give me an insight on reasons of current situation: more than one year ago, some of the main developers of Shinken left the project and made a fork named [Alignak](https://alignak-monitoring.github.io/), which is being activly developed and plan to deliver 1.0 release in December, 2016.

### Links

* [Detection and Handling of State Flapping — Shinken Manual](http://shinken.readthedocs.io/en/latest/07_advanced/flapping.html)

## [Sensu](https://sensuapp.org/)

Sensu is a monitoring framework (platform, as they call themselves) rather than complete monitoring system. Its key features include:

* Puppet \ Chef integration — define what to check and where to send messages in your configuration system
* Reusing existing technical solutions where possible, instead of inventing their own (Redis, RabbitMQ)

Sensu pulls events from queue and executes handlers on them; that’s it. Handlers can send messages, execute something on the server, or do something else you want.