Closed eswdd closed 10 years ago
Currently working in the QoS branch. Have added a capability for having ExecutionPreProcessor which will be executed both prior to enqueuing in EV queue and also post. Have added a QoSProcessor which takes a Monitor, a triggering Status and an ExecutionPreProcessor to execute when triggered. Then implementation of those requirements above become relatively simple.
TODO:
QoS branch has now been merged into master. The Monitor has been changed to a StatusSource to enable a wider range of use cases.
Have broken out the client time sections to #55 as this is less urgent.
Gist describing how to configure this: https://gist.github.com/eswdd/7683613
Marking as done since the load average monitor is not critical for the framework, only for the usecase that drove the feature. Documentation will be covered in the general doco issue #41
Various requests merge into one:
Thoughts on how to implement:
Have a list of monitors (or a status aggregator) with thresholds that cause a trigger (seperate to impact on monitoring status), and then based on that execute pieces of logic to process a request at the entry to the EV (and maybe to it's Q), to allow rejection of requests with a reason.