Bug: Composite health contributors' details are not shown
Maintainers usually reply within 1 day
@cdprete is already working on this.
Since Sep 20, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java, spring-boot
- Domain
- frontend, observability
Research direction
Compare the UI rendering with the JSON returned by the /actuator/health endpoint, focusing on CompositeHealthContributor and the discoveryComposite/discoveryClient example described in the issue. Done means the details for composite contributors are rendered in the UI rather than only their statuses.
Written by the indexing model from the issue text.
Description
Hello.
I discovered this bug while working on https://github.com/codecentric/spring-boot-admin/issues/5525 and, while we don't use (so far) composite health contributors and therefore it's not an issue for us, I decided to report this to improve the product.
Bug: If some health contributors are of type CompositeHealthContributor, the UI shows the contained contributors as separate health contributors (arguable, but out of scope here) but the details that they carry are not rendered and only their status is shown.
An example can be seen in the screenshot attached in https://github.com/codecentric/spring-boot-admin/pull/5526.
The discoveryComposite is a composite health contributor which contains the discoveryClient contributor.
For both, no details are shown even if the JSON returned by the /actuator/health call indicates there are 3 available items (the discoveryClient contributor itself plus 2 additional details).
- Dominant language
- Java
- Stars
- 12.9k
- Forks
- 3.2k
- Avg merge
- 23h 31m
- Merged PRs (30d)
- 72
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from codecentric/spring-boot-admin
-
Bug: Dependency Trees overflows the call stack on cyclic SBOM dependency graphsPossibly taken @faystmax claimed this 4 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
codecentric/spring-boot-admin#5746 ·
Maintainers usually reply within 1 day
-
Bug: Dependency Trees uses dependencies[0] as root instead of metadata.component.bom-refPossibly taken @faystmax claimed this 4 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
codecentric/spring-boot-admin#5745 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
codecentric/spring-boot-admin#5743 ·
Maintainers usually reply within 1 day
-
Bug: Filtering rules are not synchronized between SBA nodesPossibly taken @SteKoe claimed this 6 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
codecentric/spring-boot-admin#5721 · 3 comments ·
Maintainers usually reply within 1 day
-
Bug: Multiple notifications from multiple instancesPossibly taken @YadavKshitiz claimed this 8 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
codecentric/spring-boot-admin#5716 · 1 comment ·
Maintainers usually reply within 1 day
All issues in codecentric/spring-boot-admin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
java-native-access/jna#1740 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
portfolio-performance/portfolio#6119 ·
Maintainers usually reply within 8 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jenkinsci/ec2-plugin#2041 ·
-
L: github:actions L: php:composer
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
dependabot/dependabot-core#16493 ·
Maintainers usually reply within 1 day