Bug: UI broken from version 3.5.3

[cdprete]

Spring Boot Admin Server information

• Version: 3.5.3

• Spring Boot version: 3.5.5

• Configured Security: None

• Webflux or Servlet application: WebFlux

Client information

• Spring Boot versions: 3.5.5

• Used discovery mechanism: Eureka

• Webflux or Servlet application: Both

Description

Hello.

I've updated my SBA instance to 3.5.3 and now no details are shown anymore. In particular:

• The menu on the left is empty
• Instances show only their health and their metadata. No info nor anything else.

The attached picture in yellow is the "old" environment with version 3.5.2:

while the green one is the "new" environment with version 3.5.3:

What I noticed is that restarting an instance X fixes the issue for that instance, which means that the new SBA somehow doesn't handle the state properly.
Moreover, the tags in the homepage are now always gone, even for the instances which have been restarted, which is not ideal at all because then we don't know anymore about which instance we're referring to without going inside of it.

Again, in yellow the old version:

and in green the new version:

PS: the instance which has the version shown is the one that was restarted, which demonstrates the issue above about the state management and about the tags being now never shown in the homepage.

[cdprete]

/cc @SteKoe @erikpetzold since we were discussing about issues in #4646

[cdprete]

@erikpetzold @SteKoe I can confirm this occurring even with 3.5.4.

[cdprete]

Also the version of the application is not aligned anymore like before.
Now, when the group is closed, it's rendered on the right:

while when it's opened it's aligned to the left:

Of course, to get these info rendered, I had to restart the instances. :-/

[cdprete]

Ok, also in the old version they were not really aligned:

but the alignment there was a bit better (center-right jump vs left-right) since the jump in space was less.

[SteKoe]

Can you please share a screenshot of browser's network activity including the response of e.g. /info actuator? In my local test setup it looks like this:

[cdprete]

There is no call to info, metrics and so on but only to health as soon as from the homepage I got into one instance which was not restarted:

[SteKoe]

So the registration fails to expose the endpoints? See, when i check the response of /applications the instance inside of the application contains endpoints. This seems to be empty. So it is not a UI but a backend issue. Can you confirm that the data is empty in your case, too?

[cdprete]

Hi @SteKoe.

Indeed, under endpoints, only the health one is listed for the application instances which have not been restarted yet since the update to SBA 3.5.3/4.

[SteKoe]

Okay, thanks. Whenever possible, restart the instance and report, if the endpoints are registered correctly. I will discuss this internally.

[cdprete]

Okay, thanks. Whenever possible, restart the instance and report, if the endpoints are registered correctly. I will discuss this internally.

I did restart some, like HIKU KFF CALCULATOR shown previously, but only because it was the DEV environment.

We've applications which we can't just freely restart them and we can't really escalate this to business just because the new "patch" version of SBA is now completely breaking our visibility around the monitoring.

[SteKoe]

I am totally aware that this is not possible on all environments. We have a plenty of instances running ourselves and we run into the same struggle. That's why I wrote "whenever possible". :) – Anyways, we will check the endpoint detection mechanism and see, what might be the issue here.

Since you mentioned versioning of SBA, we initially started and still stick to the convention to match Spring Boot major and minor version in X.Y.z. Whereas z is our patch level. So whenever Spring Boot 3.6. will be released, SBA 3.6.0 will be shipped, too. We are also aware that this totally breaks the semantic versioning, but still think, that this is fine.