spring-cloud / spring-cloud/spring-cloud-stream
Spring Cloud 1.5.9 uses Stream, with Kafka as the binder, but health check is not taking effect.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
Spring Cloud 1.5.9 uses Stream with Kafka as the binder, but the health check is not taking effect. During the check, there is no status related to the binder. During local debugging, the class BindersHealthIndicatorAutoConfiguration is not executed at all. Checked the order of Spring configuration and found there are "not match" conditions, but the bean is still executed.
BindersHealthIndicatorAutoConfiguration:
Did not match:
- @ConditionalOnBean (types: org.springframework.cloud.stream.binder.DefaultBinderFactory; SearchStrategy: all) did not find any beans (OnBeanCondition)
Matched:
- @ConditionalOnClass found required class 'org.springframework.boot.actuate.health.HealthIndicator'; @ConditionalOnMissingClass did not find unwanted class (OnClassCondition)
- @ConditionalOnEnabledHealthIndicator management.health.defaults.enabled is considered true (OnEnabledHealthIndicatorCondition)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining BindersHealthIndicatorAutoConfiguration and the reported @ConditionalOnBean check for DefaultBinderFactory in the Spring configuration condition output. Reproduce the Spring Cloud 1.5.9 Stream setup with Kafka as the binder, then verify whether the binder health status appears during the health check. Done means the configuration executes and the health response includes binder status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100