You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Georg Henzler (JIRA)" <ji...@apache.org> on 2018/12/19 22:21:00 UTC
[jira] [Created] (FELIX-6005) Introduce result status
TEMP_UNAVAILABLE for health checks
Georg Henzler created FELIX-6005:
------------------------------------
Summary: Introduce result status TEMP_UNAVAILABLE for health checks
Key: FELIX-6005
URL: https://issues.apache.org/jira/browse/FELIX-6005
Project: Felix
Issue Type: Improvement
Components: Health Checks
Reporter: Georg Henzler
Assignee: Georg Henzler
Currently, health checks support the following result status values:
{code}
OK -> System usable
WARN -> System usable, tendency to CRITICAL (action needed to avoid this)
CRITICAL -> System not available
HEALTH_CHECK_ERROR -> Error while trying to get a status
{code}
In addition to that there should be a status
{code}
TEMP_UNAVAILABLE -> System not available, tendency to OK
{code}
See [1] for a more detailed table (DRAFT version)
This new status is similar as "Red/Amber" for traffic lights [2] (and hence AMBER is ambiguous it's better to stick with OK/WARN/CRITICAL for now instead of traffic light colors)
The table should be taken over to [3] in order to make all SPI implementors aware of the expectation their result status will come with.
[1] https://cwiki.apache.org/confluence/display/FELIXWIKI/Health+Check+Response+Status+Values
[2] https://jerseysaferoads.com/wp-content/uploads/2014/03/P6-Traffic-lights-UK.jpg
[3] http://svn.apache.org/viewvc/felix/trunk/healthcheck/docs/felix-health-checks.md?revision=1849246
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)