You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in a newly generated Sring Boot project with Release 2.3.0.RELEASE, including Web Reactive and Actuator, does not automatically provide liveness and readiness endpoints.
The docs don't suggest any additional configuration for these endpoints, as far as I understand.
boot log is
2020-05-19 16:46:44.781 INFO 3252 --- [ main] com.example.demo.DemoApplicationKt : No active profile set, falling back to default profiles: default
2020-05-19 16:46:45.824 WARN 3252 --- [ main] ion$DefaultTemplateResolverConfiguration : Cannot find template location: classpath:/templates/ (please add some templates or check your Thymeleaf configuration)
2020-05-19 16:46:45.976 INFO 3252 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path '/actuator'
2020-05-19 16:46:46.944 INFO 3252 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8080
2020-05-19 16:46:46.955 INFO 3252 --- [ main] com.example.demo.DemoApplicationKt : Started DemoApplicationKt in 2.462 seconds (JVM running for 2.797)
The text was updated successfully, but these errors were encountered:
This is a documentation bit that we've missed in this part. We've been iterating on this feature a few times and this part was left out unfortunately. I'll repurpose this issue as a documentation enhancement.
wilkinsona
changed the title
hitting http://localhost:8080/actuator/health/readiness returns 404
Document how to enable liveness and readiness probes outside of a Kubernetes environment
May 19, 2020
in a newly generated Sring Boot project with Release 2.3.0.RELEASE, including Web Reactive and Actuator, does not automatically provide liveness and readiness endpoints.
The docs don't suggest any additional configuration for these endpoints, as far as I understand.
boot log is
The text was updated successfully, but these errors were encountered: