codecentric / codecentric/spring-boot-admin
Bug: UI health state doesn't reflect the latest state
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.9k
- Forks
- 3.1k
- Avg merge
- 19h 1m
- Merged PRs (30d)
- 61
Description
Spring Boot Admin Server information
-
Version: 4.1.0
-
Spring Boot version: 4.1.0
-
Configured Security: None
-
Webflux or Servlet application: WebFlux
Client information
-
Spring Boot versions: 4.0.x
-
Used discovery mechanism: Eureka
-
Webflux or Servlet application: Servlet
Description
Hello.
It seems like the fix provided in https://github.com/codecentric/spring-boot-admin/issues/5286 is now preventing the UI to show the latest health state correctly and, instead, some stale value is getting shown.
See, for example, the picture below:
where the latest state is the one in the JSON on the right and it should, therefore, be DOWN, but the health indicator in the UI is still shown as UP.
Weird enough, the journal view doesn't show additional STATUS_UPDATED events either apart maybe the 1st one, whose payload matches the UI shown in the UI.
It's like the newer state is never produced by the SBA server, like if the StatusUpdater is stopped.
If it's not the case, then somehow the new states are not getting propagated, either in the back-end or in the UI.
Contributor 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.
Research direction
Start with the StatusUpdater and the journal view, comparing the latest health JSON with the UI indicator and emitted STATUS_UPDATED events. Reproduce the setup with the WebFlux server, Servlet client, and Eureka discovery described in the issue. Done means a current DOWN state is produced, propagated, and displayed by the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100