Monitoring Your Java Services With Dropwizard Health Checks
Troubleshooting applications can be tedious and time-consuming. It generally involves checking application logs, networking, firewalls, databases, database logs, third-party services, internal service logs… you get the idea. When service is interrupted every second can count. Let your application help you track down issues faster. Your application already has configurations set up for connecting to each external service you need. Why not spend a few extra minutes and make your life a little easier.
What Is a Health Check?
Health checks are generally very simple binary checks. A check can be as simple as a ping command. This covers two troubleshooting use cases. Can we connect to the service and is that service operational? A failing check won’t tell you what is wrong, but it can quickly point you in the right direction. Health checks can also be used for preventing and automatically resolving some issues. If you have auto scaling or load balancers that monitor an application’s health, they can quickly add/remove servers when there are issues. As with all fully automated systems, this could backfire and accidentally remove all the servers when minor hiccups occur. This is one reason health checks are recommended to be used for simple up/down checks and not for variable/metric-related checks.
via DZone.com Feed https://dzone.com
May 19, 2017 at 08:09AM