2.82. MicroProfile Health
Expose Camel health checks via MicroProfile Health
2.82.1. What’s inside 复制链接链接已复制到粘贴板!
Refer to the above link for usage and configuration details.
2.82.2. Maven coordinates 复制链接链接已复制到粘贴板!
Create a new project with this extension on code.camel.redhat.com
Or add the coordinates to your existing project:
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-microprofile-health</artifactId>
</dependency>
2.82.3. Usage 复制链接链接已复制到粘贴板!
You can register health checks for your applications with the Camel health check API.
By default, classes extending AbstractHealthCheck are registered as both liveness and readiness checks. You can override the isReadiness method to control this behaviour.
Any checks provided by your application are automatically discovered and bound to the Camel registry. They will be available via the Quarkus health endpoints /q/health/live and /q/health/ready.
You can also provide custom HealthCheckRepository implementations and these are also automatically discovered and bound to the Camel registry for you.
Refer to the Quarkus health guide for further information.
2.82.3.1. Provided health checks 复制链接链接已复制到粘贴板!
Some checks are automatically registered for your application.
2.82.3.1.1. Camel Context Health 复制链接链接已复制到粘贴板!
Inspects the Camel Context status and causes the health check status to be DOWN if the status is anything other than 'Started'.
2.82.3.1.2. Camel Route Health 复制链接链接已复制到粘贴板!
Inspects the status of each route and causes the health check status to be DOWN if any route status is not 'Started'.
2.82.4. Additional Camel Quarkus configuration 复制链接链接已复制到粘贴板!
| Configuration property | Type | Default |
|---|---|---|
|
Set whether to enable Camel health checks |
|
|
Configuration property fixed at build time. All other configuration properties are overridable at runtime.