Skip to content

Bug: Additional DiskSpaceIndicators are not rendered in a human-readable way #4289

Open
@cdprete

Description

@cdprete

Spring Boot Admin Server information

  • Version: 3.4.6

  • Spring Boot version: 3.4.5

  • Configured Security: None

  • Webflux or Servlet application: WebFlux

Client information

  • Spring Boot versions: 3.4.5

  • Used discovery mechanism: Eureka

  • Webflux or Servlet application: Servlet

Description

As shown in the picture below, if additional DiskSpaceIndicator s are added to to the health, the sizes that they expose are not formatted in a human-readable format like it happens for the diskSize instead that comes from Spring Boot itself.

Image

While I would assume that would not really be achievable out of the box, what do you think about the idea of having the clients indicating in their metadata if custom health indicators are present and what their format should be?

E.g:

metadata-map;
    health-indicators:
         data: diskSpace

where data is the name of the health indicator while diskSpace is the format of the response it returns.
Of course, the format then has either to match one of the standard health indicators or have the value custom to render it as it is.
In the case where the health indicator is not communicated by the client, then the current logic applies.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions