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 #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.
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 #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_UPDATEDevents 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.