Hello :) This was also posted on github
[here](https://github.com/naparuba/shinken/issues/1238).
I am proposing the addition of a new optional daemon to Shiknen, the
__analyst__.
##### This new component would allow for the following functionalities:
* Make bprules on metrics and statuses
* Generate alerts on unconfigured services and on passive configured services
(ex: collectd)
* Make trending analysis on any metrics or combination of metrics.
* Possibly generate alerts and make bprules on services and statuses from
different realms
* Generate new metrics based on a mix of other metrics
##### It would cover the following use cases:
* Extend the capabilities of bprules.
* For example: Two switches are connected together with two cables. I want to
monitor the bandwidth usage of both cables. Currently, bprules won't give me a
good idea of total usage. It would be appropriate to merge both metrics:
Instead of 99% (cricial) and 0%(ok), just tell me 49%.
* In a large automated environment, it is complicated to configure hosts as
they come and go. This is where passive monitoring comes in handy. However, I
have to configure individual hosts if I want to receive alerts. I would like to
define rules like the following: If load is above a certain threshold on any of
my servers (configured or not), generate an alert.
##### How the daemon would fit in the current data flow:
1. The user creates rules and configures the analyst.
2. From these rules, the arbiter configures the brokers so that they keep the
necessary data in dedicated queues for the analysts.
3. Receiver/Poller receives check results.
4. The broker polls the check results broks and sends them to the database
5. Before deleting the broks, the broker checks his config for analysts that
requires them and puts the broks in dedicated queues.
6. The analyst retrieves the broks from the appropriate brokers and analyses
them. If necessary, it generates new broks/alerts.
##### Details:
* A check result could be required by several analysts, the brokers keep one
queue per linked analyst.
* At first, the rules would be written in Python and evaluated by the daemon.
In the future, this would become modular and rules could be written with any
syntax (Ex: lua).
* Analysts could analyses metrics generated by other analysts. They could also
generate metrics based on analyst-generated metrics!
The analyst would greatly enhance Shinken's alerting capabilities and would
also simplify alerting on passive results.
I would like to propose myself as the main developer for this new daemon, I
would be working on this at Savoir-Faire Linux where we already have two other
Shinken specialists and contributors.
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
