[
https://issues.apache.org/jira/browse/CAMEL-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136306#comment-16136306
]
Luca Burgazzoli commented on CAMEL-10026:
-----------------------------------------
Yeah there will be an UNKNOWN state, like what spring-boot does which does not
affect the overall application status.
About the registry, I did't include it by default in the initial implementation
so components don't always put stuffs in there when health-checks are not in
use, maybe we can also add an option like enable/disable health checks but the
final result would be similar to have/not have the registry. I think having it
by default may be postponed to 3.0 were we should have also an internal
[registry|https://issues.apache.org/jira/browse/CAMEL-10792] we can leverage
and maybe a better way to control the service we want to enable/disable, make
sense ?
> HealthCheck API
> ---------------
>
> Key: CAMEL-10026
> URL: https://issues.apache.org/jira/browse/CAMEL-10026
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Luca Burgazzoli
> Labels: health-check
> Fix For: 2.20.0
>
>
> Add a health check API to camel-core so this API can be queried from Java /
> JMX / spring-boot etc. so users can easily get a health check. This can be
> used for liveness/readiness checks for their Camel apps.
> The API should allow optional support for components to implement custom
> logic for health check. So a FTP component can connect to a FTP server and do
> a FTP list etc. A JDBC component does a SQL query, and so on.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
