Uptime: Health Check Endpoint Explained
You need to know if your application is up and running. When your system has trouble, you need to be alerted so you can fix it before it affects customers. Health checks are quick and easy ways to monitor your application. Let’s dive in.
What is a Health Check Endpoint?
Health check endpoints are HTTP endpoints created for uptime monitoring. (e.g. app.myservice.com/health) In health check endpoints you’ll run a series of basic tests. Are my components (database, file system…) working? If everything passes the test, the endpoint returns an HTTP 200. It’s a good idea to also include a breakdown of the test results in the response. That makes debugging things easier down the road.
Where should I use Health Checks
Health check endpoints are helpful, but they aren’t a perfect test. Your database may be responding to pings, but failing on inserts. The file system may show that you have permission, but it may be out of disk space.
Think of a health check like checking your temperature. If you have a fever, something is definitely wrong. But, if you don’t have a fever, that doesn’t mean everything is ok. Health checks are helpful, but real data checks are where it’s at.
One last thing on health checks. If you have the engineering resources, this is something you should setup. It’s pretty minimal effort compared to a real data check. And, it’s much more thorough than a smoke check.
If you enjoyed this article, you may also enjoy