You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Clinton H Goudie-Nice (JIRA)" <ji...@apache.org> on 2017/05/12 23:45:04 UTC

[jira] [Created] (SLING-6855) Create ResultRegistry to provide health check behavior for executing code that does not want a HealthCheck

Clinton H Goudie-Nice created SLING-6855:
--------------------------------------------

             Summary: Create ResultRegistry to provide health check behavior for executing code that does not want a HealthCheck
                 Key: SLING-6855
                 URL: https://issues.apache.org/jira/browse/SLING-6855
             Project: Sling
          Issue Type: New Feature
          Components: Health Check
            Reporter: Clinton H Goudie-Nice


I want to provide a Registry service that can be leveraged to provide health check results.
These results can be for a period of time through an expiration, until the JVM is restarted, or added and later removed.

This can be useful when code observes a specific (possibly bad) state, and wants to alert through the health check API that this state has taken place.

 Some examples: 
 An event pool has filled, and some events will be thrown away.
  This is a failure case that requires a restart of the instance.
  It would be appropriate to trigger a permanent failure.
   
 A quota has been tripped. This quota may immediately recover, but it is sensible to alert for 30 minutes that the quota has been tripped.

 If you expect the failure will clear itself within a certain window, setting the expiration to that window can be ideal.

GHPR to follow



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)