HealthAutoConfiguration
The node's health in Spring Boot Actuator, when the application has Actuator's health support (spring-boot-starter-actuator), unless wow.health.enabled=false (HealthProperties):
a NodeHealth of the node, sampling from the bean's start to its end (it samples nothing while the node does not run);
the contributor
wow: one indicator per component (node,ownership,stores,topics,subscriptions,executor,liveness), eachUP,DEGRADED(Spring Boot's status aggregation leaves it out, so it does not change a group's status) orDOWN, the parts of each in its details; andqueries, alwaysUP, each store's query bulkhead (its limit and write pressure), which no probe group reads;wowReadiness, NodeHealth.readiness, andwowLiveness, NodeHealth.liveness, which HealthGroupsEnvironmentPostProcessor adds to Actuator's availability probe groups:/actuator/health/readinessisreadinessStateandwowReadiness,/actuator/health/livenessislivenessStateandwowLiveness;/actuator/health/wowis thewowcontributor (a group cannot share its name).
What a response shows beyond the status follows Actuator's own rules (management.endpoint.health.show-details, never by default, and the web exposure): the host exposes no detail on the public port the application did not ask for, and the details hold no message or address, only counts, states and exception class names.
Functions
wow: every component of the node's health, and queries, the stores' query bulkheads, when the node queries its stores: always UP, its details each store's limit and write pressure.
wowLiveness: whether the node is stuck.
wowReadiness: whether the node can serve traffic.