[
https://issues.apache.org/jira/browse/CAMEL-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137748#comment-16137748
]
Claus Ibsen commented on CAMEL-10026:
-------------------------------------
Okay that is fine with UNKNOWN state.
Okay its just that most of those global cross functional services with the
current api have a default implementation OOTB and then you can plugin a custom
by just adding a bean to the registry etc, eg typically those SPI interfaces.
With an Optional<x> then that API would be a little bit different. But I guess
if we make it OOTB in Camel 3.0 then its okay for now.
> 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)
