opened
rgeniesse
username_0
<!--- Provide a general summary of the issue in the Title above -->

## Expected Behavior
After a check goes into a non-ok state, the check interval should have the ability to increase. This lets you have more confidence that there is actually an issue going on in a sense.

## Current Behavior
Check interval is static without using either outside configuration management to increase the interval or a separate check/ check hook to call the API to increase the interval, then when resolved decrease the interval.

## Possible Solution
Add the feature!

## Context
See https://discourse.sensu.io/t/sensu-check-different-retry-interval-on-failure/1152 for the source of the FR.

I believe Nagios has a similar concept.
Feature Request: check retry interval when in a non-ok state
issue
created
majormoses
username_1
I have seen this request come up multiple times in sensu ruby and now in sensu-go. I think it makes a lot of sense as you want to know once it reaches a healthy state in a timely manner even if there is a long interval. There are some performance considerations as say a core networking component suddenly fails and now you have `n` number of checks that are running at shorter intervals leading to increased load.
comment
created
nicolasbrechet
username_2
Hi,

This is a feature that would be very interesting for me... Going from icing to Sensu...

Any chance it could be considered for development ?
comment
created
majormoses
username_1
I am not an employee of sensu, I would love this feature myself. It is a small but very welcome quality of life improvement for sensu.
comment