anchor.diff:  [%header,cols=3*]
   |====
   | Name | Default | Description
  +| parent |  | The parent group this health check belongs to, such as context, routes, or consumers.
   | enabled | true | Set if the check associated to this configuration is enabled or not.
  -| interval | | Set the check interval in milliseconds.
  -| successThreshold | | Set the number of success before reporting the service as healthy.
  -| failureThreshold | | Set the number of failure before reporting the service as un-healthy.
   |====
  -
  -The `interval`, `successThreshold`, and `failureThreshold` are used for configuring health checks to deal with flaky checks.
  -For example assume you do not want to regard a check as immediately DOWN when a check for the first time returns a response as DOWN.
  -So you can specify the `interval=10000` and `failureThreshold=5`, which means that the check has slacks, and will
  -only report it as DOWN when there has been 5 failures in a row, with a minimum of 10 second of interval between these checks.
  -So in other words after minimum 50 seconds and 5 calls then it can be reported as DOWN.
  -
  -The `successThreshold` is used for number of successful checks in a row before the check is regarded as UP.
  -By default, this is not in use, and the first successful check will result in UP.
   
   == Configuring health-check
   
  
positive.code: Camel provides the following health checks out of the box:
  
  - _context_ - A `HealthCheck` which performs check whether the `CamelContext` is started. This can be used for readiness checks; to know when Camel is fully started and ready to handle traffic.
  - routes - A `HealthCheckRegistry` which discovers all the available routes in `CamelContext` and checks whether they are all started.
    This can be used for readiness checks; to know when Camel is fully started and ready to handle traffic.
    Combining with the supervised `RouteController` this allows to perform readiness check for routes that are under supervising,
    such as troublesome routes that may not start up the first time, and are retried to be started in the background with backoff delays.
  
negative.code: camel.health.config[kafka*].enabled=false
  camel.health.config[*].parent=routes
  camel.health.config[*].enabled=true
  ----
  
  === Turning off consumer level health-checks
  