Frédéric MOHIER

Thanks for reporting. Which commands are you interested with ? Please list...

I had a look on how to implement these external commands and it is not an easy job... this will be implemented in a next version

I suppose this is a problem with the backend retention module that stores a lot of in-progress notifications. As of now: ``` { "notifs": { "e3f387c440644d18a98a861797554892" : { "reason_type" :...

To be confirmed with the new retention strategy implemented in the Alignak backend as of today

Currently on my server: ``` [2017-09-01 11:20:56 CEST] INFO: [alignak.scheduler] Orphaned action (300 s / 1501674371.91 / 1504257656) action for: ek3022fdj-00009/nsca_services (Notification 5f87ffe0146a41fcb0fa37998a986ede type:PROBLEM status:inpoller command:/usr/local/var/libexec/alignak/notify_by_email.py -t service -S mail.ipmfrance.com...

Some enhancements ideas: - [ ] : provide a livesynthesis history as a timeseries - [ ] : provide a timeseries with the alignak daemons status

This could be linked with the `date_format` property that exists in the main configuration file ...

@ddurieux : manage this in the Alignak backend ?

Thanks for reporting. And, yes, the package should depend on `python3-pip` but I did not yet managed the dependencies.

@ddurieux : pyopenssl version ?