alignak
alignak copied to clipboard
Monitoring tool, highly flexible and new standard oriented
This issue to sum-up the Alignak states management made for the hosts and services. **Initial state:** A new host/service that has not been checked is set in its configured `initial_state`....
Currently, the daemons may call some hook functions implemented in the modules but there is no management of any function return code. Thus, a retention data loading function of external...
What is to be done when: - a daemon is killed - a module is killed The daemon test process should be: - try every second - stop 5 seconds...
For now, the broks from scheduler are sent to all brokers. I propose to keep this behavior (because some module can need get all broks) and add possibility to define...
This feature (inherited from Shinken) is not currently implemented in the Alignak scheduler. Neither, it was not implemented in Shinken ... despite the fact that it is documented and described...
On the demo configuration (realms *North* and *South*, children of default realm *All*), with 2 receivers (*All* and *North*), the external commands do not propagate, except for the realm *All*...
Currently the retention store is included in the scheduler main loop and executed as a loop action when the time comes to store the retention (according to Alignak configuration parameter)....
When several Alignak same daemon are started, it is quite messy to get-off this mess ... It may be interesting, if possible, to alert and protect against this situation. Checking...
It could be nice to manage the lang of user, it can be used for webui, for notifications...
Whe nthe Arbitr is checking the configuration, it should check that the required plugins for the commands are available. This will prevent from errors in the poller on execution ...