[
https://issues.apache.org/jira/browse/CAMEL-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136044#comment-16136044
]
Claus Ibsen commented on CAMEL-10026:
-------------------------------------
I wonder if the state of only UP or DOWN is too limited. What if a component is
being initailized, then it would be DOWN at the moment, as its not yet up and
running. Maybe we need a 3rd state to indicate its not active/started etc. UP,
DOWN, NOT_ACTIVE etc. And yeah naming can be hard so to come up with a good
name for that 3rd state.
Also I wonder if we do not want to always include a default health check
registry, so it can do a basic check of camel context itself. Always having
such a service brings more benefits as users can rely on that the API is there
and in use, and they can use the API, JMX, etc. Many of the existing camel
services have a default implementation OOTB.
> 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)
