Health Probes Should Not Follow Redirects Blindly
A probe that follows a redirect can report success for the wrong endpoint and hide an authentication or routing failure.
A probe that follows a redirect can report success for the wrong endpoint and hide an authentication or routing failure.
Restarting a service whenever one of its dependencies is temporarily unhealthy is not always helpful. An external failure may not be fixed by restarting the application, and useful in-flight work can be lost in the process.
A synthetic health request measures the service only if it looks like a request the service considers valid.
Browser security policy is part of application behavior; a blocked fetch can make a healthy backend look unreachable.
A running process is useful information, but it does not prove the process is completing the work it exists to do. A web server can be alive while its required database is unreachable.