{{announcement.body}}
{{announcement.title}}

Helidon: Microservice Health Check

DZone 's Guide to

Helidon: Microservice Health Check

A health check of our Microservice is part of Microprofile specification. We don't need to write anything special with Helidon.

· Microservices Zone ·
Free Resource

Helidon health check graphic

Learn how to perform a health check with Helidon.

A health check of our Microservice is part of Microprofile specification. We don't need to write anything special with Helidon. All the health API will be available out of the box in our implementation.

Health Check APIs

There are three endpoints are available as part of the specification to check the health of our microservices. These APIs will be used by the 3rd party application/integration tools to check the health. Those APIs are as follows,

/health /health/live /health/ready


You may also like: Dockerized App With Java Module System, Helidon, and Alpine-Based JDK 12 EA

/Health

This is the top-level API to check the health of our microservice. Apart from the liveness and readiness of our application, we will also get more internal information about services like the following,

/Health/Live

We can check the liveness of our application using this end-point. Any micro profile compliant framework should offer this implementation out of the box. Helidon will also offer such end-point and return meaningful information. In some cases, we may need to customize the liveness end-points.

In such use-cases, we need to provide an implementation of the HealthCheck interface with @Liveness annotation. See the code below.

//Custom Liveness implementation @Liveness @ApplicationScoped 
//public class DailyApiLiveness implements HealthCheck { 
//@Override public HealthCheckResponse call() { return 
//HealthCheckResponse.named("DailyAPI Liveness") .up() 
//.withData("time", System.currentTimeMillis()) .build(); } }

/Health/Ready

This end-point is similar to the above live end-point. The only difference is the @Readiness annotation instead of @Liveness. We can add our custom logic to calculate the readiness to expose the real value to our partners or integration solutions. Please see the sample code below,

//We can add our custom logic to calculate the real readiness and 
//return the response //accordingly. @Readiness @ApplicationScoped 
//public class DailyApiReadiness implements HealthCheck { 
//@Override public HealthCheckResponse call() { return 
//HealthCheckResponse.named("DailyAPI Readiness") .up() .build(); } }


Once everything is set properly, we will get the following response when we access the /health API.

{ "outcome": "UP", "status": "UP", "checks": [ { "name": "DailyAPI Liveness", 
  "state": "UP", "status": "UP", "data": { "time": 1571677530451 } }, 
{ "name": "DailyAPI Readiness", "state": "UP", "status": "UP", "data": 
 { "time": 1571677530460 } }, { "name": "deadlock", "state": "UP", "status": 
  "UP" }, { "name": "diskSpace", "state": "UP", "status": "UP", "data": 
  { "free": "96.31 GB", "freeBytes": 103412359168, "percentFree": 
       "41.23%", "total": "233.57 GB", "totalBytes": 250790436864 } }, 
   { "name": "heapMemory", "state": "UP", "status": "UP", "data": 
    { "free": "194.89 MB", "freeBytes": 204357016, "max": "1.78 GB", 
     "maxBytes": 1908932608, "percentFree": "98.02%", "total": "231.00 MB", 
     "totalBytes": 242221056 } } ] }


I hope you have enjoyed the article. Let me know if you need any improvement or suggestion on this topic.

Happy coding!


Further Reading

MicroProfile: What You Need to Know

Choosing a REST Framework for Microservices

Thoughts on Quarkus

Topics:
microservices ,helidon ,apis ,health check ,endpoints

Published at DZone with permission of Thamizh Arasu , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}