codecentric / codecentric/spring-boot-admin
Bug: Instance reported as down even if it's up
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: 3.5.2
-
Spring Boot version: 3.5.5
-
Configured Security: None
-
Webflux or Servlet application: WebFlux
Client information
-
Spring Boot versions: 3.5.3
-
Used discovery mechanism: Eureka
-
Webflux or Servlet application: Servlet
Description
Hello.
I've the weird behaviour that an application is reported as DOWN in SBA even if its health endpoint reports it as UP.
Moreover, I can see in the HTTP Exchanges view that the health has been indeed called and that it returned 200, but somehow it's not reflected in the status of the application.
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
No files, tests, or entry points are named. Start by reproducing the reported status mismatch with Spring Boot Admin 3.5.2, Spring Boot 3.5.5, a WebFlux server, and an Eureka-discovered Servlet client; trace how the 200 health response becomes the displayed status. Done means the instance is reported UP when its health endpoint returns UP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100