From 385346f9ede4a34bc6d39ee11a1bd52dc2d1d9db Mon Sep 17 00:00:00 2001
From: Jim Martens <github@2martens.de>
Date: Tue, 7 Jul 2020 22:18:33 +0200
Subject: [PATCH] Updated documentation for REST health check and changed
 method name

---
 .../templateservice/actuator/RestHealthCheck.java    | 12 ++----------
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/template-server/src/main/java/de/twomartens/templateservice/actuator/RestHealthCheck.java b/template-server/src/main/java/de/twomartens/templateservice/actuator/RestHealthCheck.java
index 608bdca..02aef92 100644
--- a/template-server/src/main/java/de/twomartens/templateservice/actuator/RestHealthCheck.java
+++ b/template-server/src/main/java/de/twomartens/templateservice/actuator/RestHealthCheck.java
@@ -14,15 +14,7 @@ import org.springframework.web.client.RestTemplate;
 import java.util.Optional;
 
 /**
- * A Healtcheck which checks if the rest services are working.
- *
- * If you have a complex service behind grpc, you should think about an easy greeting or echo service, which only tests
- * the network/service stack and not the full application.
- *
- * The healthcheck will be called by kubernetes to check if the container/pod shuold be in loadbalancing. It is possible
- * to have as much healthchecks as you loke.
- *
- * There should be a healtcheck which is ok not before all data is loaded.
+ * A Health check which checks if the rest services are working.]
  */
 @Slf4j
 @Component
@@ -55,7 +47,7 @@ public class RestHealthCheck extends AbstractHealthCheck implements HealthIndica
 
   @Override
   String getMethodName() {
-    return "infodb-rest";
+    return "template-service-rest";
   }
 
   String mkEndpoint() {