Spring Cloud 1.5.9 uses Stream, with Kafka as the binder, but health check is not taking effect.

Open
#3,159 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, spring
Domain
backend, observability

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.

Description

waiting-on-feedback

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)

Dominant language
Java
Stars
1.1k
Forks
646
Avg merge
2d 3h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-stream

All issues in spring-cloud/spring-cloud-stream

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.