Microprofile Health

Since Camel 3.0

The microprofile-health component is used for bridging Eclipse MicroProfile Health checks with Camel’s own Health Check API.

This enables you to write checks using the Camel health APIs and have them exposed via MicroProfile Health readiness and liveness checks.

Maven users will need to add the following dependency to their pom.xml for this component:

    <!-- use the same version as your Camel core version -->


By default, Camel health checks are registered as both MicroProfile Health liveness and readiness checks. To have finer control over whether a Camel health check should be considered either a readiness or liveness check, you can extend AbstractHealthCheck and override the isLiveness() and isReadiness() methods.

For example, to have a check registered exclusively as a liveness check:

public class MyHealthCheck extends AbstractHealthCheck {

    public MyHealthCheck() {

    protected void doCall(HealthCheckResultBuilder builder, Map<String, Object> options) {
        builder.detail("some-detail-key", "some-value");

        if (someSuccessCondition) {
        } else {

    public boolean isReadiness() {
        return false;

Auto discovery

The expectation is that this component is run within a MicroProfile container, where CDI and a library implementing the MicroProfile health specification is available. E.g SmallRye Health.

In this scenario, the readiness and liveness checks are automatically discovered and registered for you.

However, it’s still possible to manually register Health checks without CDI. Ensure your camel health checks are available in the Camel registry and add an instance of CamelMicroProfileReadinessCheck and CamelMicroProfileLivenessCheck to the health check registry of your MicroProfile Health implementation.