I have seen numerous articles and posts on this topic and they seem all to do it differently and in many cases the suggested solution was unclear or was not working. Some of the solutions worked but seemed to do more than required.

I have seen numerous articles and posts on this topic and they seem all to do it differently and in many cases the suggested solution was unclear or was not working. Some of the solutions worked but seemed to do more than required.

It could be a silly question, but I searched online and wasn’t able to find any details on the difference of spring-boot-actuator and spring-boot-starter-actuator.

I am trying to analyse whether or not to use “/actuator/health/liveness” and “/actuator/health/readiness” instead of “/actuator/health”. I mainly used https://spring.io/blog/2020/03/25/liveness-and-readiness-probes-with-spring-boot for information.

I have created a very simple Spring / Boot sample application to test how the liveness and readiness probes work. I configured both Spring Boot 2.7.18 and 3.2.5 In my application properties, I have

the /actutor/health endpoint in my application returns status for all the components in our app and the overall status. When a component is not available, it’s status changes to DOWN and the overall status changes to DOWN as well.

My application uses the following Spring Boot property management.metrics.web.server.request.autotime.enabled. it’s listed as deprecation in v3.2.6 with message Should be applied at the ObservationRegistry level. What does this message mean and how do I apply this property at the ObservationRegistry level.

The application is hosted in cloud foundry and when I try to update the log level configuration of the application using the actuators api –> /actuators/loggers/ROOT, response is 204. But after few seconds, log configurations gets reset to default, i.e. INFO

I am trying to write my own endpoints to return SpringBoot Actuator liveness and readiness status over /ready, /live and /health without exposing any default endpoint from Actuator dependency.

Using Spring 2.7 with micrometer and prometheus. I have refactored one of my autoconfiguration classes to use RestTemplateBuilder instead of RestTemplate.
With this change, the jvm metrics are no longer available.