[
https://issues.apache.org/jira/browse/FELIX-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733951#comment-16733951
]
Georg Henzler edited comment on FELIX-6005 at 1/4/19 9:02 AM:
--------------------------------------------------------------
Fixed in [r1850329|http://svn.apache.org/r1850329]
* Added new status TEMPORARILY_UNAVAILABLE to Result.Status
* FormattingResultLog has a the method temporarilyUnavailable(...)
* Increased default width for result column of verbose text serialiser
* Added table from [1] to documentation
* new status can also be created via JMX bean
org.apache.felix.healthcheck:type=AdjustableStatusHealthCheck
* Adjusted HealthCheckResultCache to also make TEMPORARILY_UNAVAILABLE stick if
"hc.warningsStickForMinutes" is used
was (Author: henzlerg):
Fixed in [r1850329|http://svn.apache.org/r1850329]
> Introduce result status TEMPORARILY_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
> Priority: Major
>
> Currently, health checks support the following result status values:
> {code:java}
> OK -> System usable
> WARN -> System usable, tendency to CRITICAL (action needed to avoid CRITICAL
> in future)
> 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:java}
> TEMPORARILY_UNAVAILABLE -> System not available, tendency to OK (will become
> OK without action after some time)
> {code}
> Potential examples for status TEMPORARILY_UNAVAILABLE (-was initially
> TEMP_UNAVAILABLE-, updated due to [~joerghoh]'s feedback):
> * System startup
> * Deployment (update of bundles/configs)
> * Health check checking availability of remote system that returns 503
> 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)
