On 6 Jul 2017, at 15:00, David Lloyd wrote: > > Is this a polling-only service, or is there a "push" mechanism? Right now poll only, basically building the counterpart of the Kubernetes/OpenShift health check calls. > Just brainstorming, I can think of a few more potentially useful health > checks beyond what you've listed: > > • EJB failure rate (if an EJB starts failing more than some percentage of > the last, say 50 or 100 invocations, it could report an "unhealthy" > condition) > • Database failure rate (something with JDBC exceptions maybe) > • Authentication realm failure rate (Elytron's RealmUnavailableException) I think those are internal implementation details and something each application needs to come up with good values. While the HCP can have a detailed payload as above, it is not required, and could only return 204 UP or 503 DOWN. Kube will not look at the body anyway.