[
https://issues.apache.org/jira/browse/CAMEL-17839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511341#comment-17511341
]
Roger Goossens commented on CAMEL-17839:
----------------------------------------
Hey [~davsclaus] , yeah we are using Spring Boot and we are using
implementations of Spring's HealthIndicator for our custom checks, not Camel
HealthChecks, so I can imagine that Spring's liveness and readiness could be
out of sync with the subset of HealthChecks Camel performs in our applications.
At this moment our biggest issue is that scheduled polling consumers used to
have a Status of UP after the application starts and now they are DOWN until
something actually gets polled. So for now we've excluded those health checks
(via the camel.health.config property) from participating in the overall
status. But we like to put them back in, and an initial status of UNKNOW
instead of DOWN would fix that imho.
I'll see if I can put together a small service that combines all. Give me a day
or two.
Cheers, Roger.
> camel-health - Route health check - allow to configure initial state
> --------------------------------------------------------------------
>
> Key: CAMEL-17839
> URL: https://issues.apache.org/jira/browse/CAMEL-17839
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.17.0
>
>
> Some users may have monitoring systems that rely on camel-health report UP on
> initial startup - as they may not differentiate between a readiness vs
> liveness check.
> See comments on CAMEL-17168
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
