[
https://issues.apache.org/jira/browse/UNOMI-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889143#comment-17889143
]
Jerome Blanchard commented on UNOMI-854:
----------------------------------------
Small improvements to ease the usage of health-check extension :
* Use a different HTTP response code that 200 when not all checks are LIVE
* Ensure a fix order in the healthcheck provider response.
* Add the health password config in the custom.system.properties to allow
override using Environment variable UNOMI_HEALTHCHECK_PASSWORD
> Add Healthcheck endpoint
> ------------------------
>
> Key: UNOMI-854
> URL: https://issues.apache.org/jira/browse/UNOMI-854
> Project: Apache Unomi
> Issue Type: Improvement
> Components: unomi(-core)
> Reporter: Jerome Blanchard
> Assignee: Jerome Blanchard
> Priority: Major
> Fix For: unomi-2.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Add a /health route in unomi to get status of the application
> The health endpoint should include informations about :
> status of the application (started/not started, ram, cpu, bundles sarted)
> status of underlying systems (cluster status, es connection status)
> Any informations gathered must be gathered quickly and not be blocking in any
> case. Thus if a subsystem does not respond quickly, a specific status should
> be returned.
> Structure of the response could include subresources in order to have a very
> small respond time on the basis request.
> Have a look on any other health check system like quarkus q
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
