[SLING-6855] Sticky Results Support

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Health Check Annotations 1.0.6, Health Check Core 1.2.10, Health Check API 1.0.2
• Component/s: Health Check
• Assignee: Unassigned
• Reporter: Clinton H Goudie-Nice
• Created: 12/May/17 23:44
• Updated: 29/Nov/17 23:38

Description

Introduce HC service property hc.warningsStickForMinutes to allow old WARN/CRITICAL/HEALTH_CHECK_ERROR results to be sticky (see also http://sling.markmail.org/thread/tawikgt7bqxvnlj5#query:+page:1+mid:57hhg55hekr7ib33+state:results)

— Original Request ----
Create ResultRegistry to provide health check behavior for executing code that does not want a HealthCheck

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

Issue Links

• is related to: SLING-7246 Document changes for SLING-6855 and SLING-6946
• links to: GitHub Pull Request #228