Fess

Tangentially related, nagios has this feature. It has a `check_interval` and a [`retry_check_interval`](http://nagios.manubulon.com/traduction/docs14en/checkscheduling.html#service_options). The retry check interval can be more frequent which allows for less frequent checking but more frequent...

There's a related concept here. in sensu there is only the stash. in nagios there is "Ack" and "downtime" I've since realized that sesu's stash is currently equivalent to nagios...

adding the idea of acknowledge vs downtime to sensu-handler https://github.com/sensu-plugins/sensu-plugin/pull/135 with the idea of acknowledgment vs downtime handle this way. triggering an event on stash can be independent of that...

brainstorming: after spelunking the code. I'm currently thinking about two approaches. 1. the sensu-api creates a check event with a preconfigured handler "stashes" and pushes it to the transport similar...

a proper acknowledgment discussed and resolved in built in silencing issue https://github.com/sensu/sensu/issues/1328 and implementation https://github.com/sensu/sensu/pull/1400 with the introduction of `expire_on_resolve` that was a bit of a tangent on this issue....

Anyone ever open a bug for this issue on [bugzilla](https://bugs.exim.org/ )? I couldn't find one to link here. may also be why the issue has stagnated. > Our bug-tracker takes...