With WFLY-12228, WildFly 18 will provide HTTP endpoints for MicroProfile Health 2.0.1.

This major release introduces changes in these HTTP endpoints:

• the existing /health endpoint now checks both liveness and readiness probes
• the new /health/live endpoint checks only liveness probes
• the new /heatlh/ready endpoint checks only readiness probes

Note that they are corresponding DMR operations for these 3 probes:

• the existing :check operation now checks both liveness and readiness probes
• the new :check-live operation checks only liveness probes
• the new :check-health operation checks only readiness probes

The EAP script that checks for server liveness[1] should be updated to use the :check-live operation.

The EAP script that checks for server readiness could be enhance to use the :check-ready operation to take into account application readiness.
Note that there would need to have some user configuration required to take into account the readiness check.
By default, the app server reports that the server is ready (as soon as the health subsystem is started). This might lead to false information if the server reports its it ready before the application deployed is installed and actually ready.
The health subsystem has a empty-readiness-checks-status that be can set to DOWN to report that the server is not ready if there are no registered health checks probes.

This means that to take into account the readiness probe from the health subsystem, the user MUST:

• set empty-readiness-checks-status to DOWN
• provide a readiness probe to detect when his or her application is ready

[1] https://github.com/jboss-container-images/jboss-eap-modules/blob/master/os-eap-probes/2.0/added/probes/probe/eap/dmr.py#L163