management.endpoint.health.group.liveness.show-details=always
management.endpoint.health.group.readiness.show-details=always
management.endpoint.health.probes.add-additional-paths=true
management.endpoint.health.probes.enabled=true
management.server.port=8081
Via @dsyer, with these properties, the probes are not available at :8080/livez and :8080/readyz. Commenting out the show-details properties fixes the problem. The same problem occurs when configuring management.endpoint.health.group.liveness.include and management.endpoint.health.group.readiness.include.
Comment From: wilkinsona
@malachispencer As far as we know, this should work unless you have configured any management.endpoint.health.group.liveness.* or management.endpoint.health.group.readiness.* properties. If you have seen behavior that is different to that, can you please share a minimal sample that we can look at?
Comment From: wilkinsona
@malachispencer I see that you have also asked on Stack Overflow. To avoid wasting people's time due to duplication of effort, please continue this over there.
Comment From: ChristianCiach
I just wasted an hour on trying to figure out why /readyz gave me a 404 just because management.endpoint.health.group.readiness.include has been configured.
This issue can be workarounded by setting the additional paths explicitly:
management.endpoint.health.group.liveness.additional-path=server:/livez
management.endpoint.health.group.readiness.additional-path=server:/readyz