But definitely right that it doesn’t call application logic especially db layer if eg on Amazon you are doing db maintaince upgrades if db aliveness is part of aliveness check you can have problems with containers being restarted when there is nothing wrong with the app itself so definitely lean and lucee focused and obviously the route / path excluded from any upstream or nginx cache that you may operate

Yeah this is exactly what we are dealing with. "you can restart as much as ya bloody like, but that is not gonna fix the DB being down, so stop it!" I blame the idiot that set up the first iteration of our docker health checks. That guy is a dick. ✋