How do you monitor Apache Camel using JMX, Camel Management, and Micrometer?

Camel exposes runtime metrics and management operations through three layers:

• JMX (Java Management Extensions): Enabled by default. Each CamelContext, Route, Endpoint, and Processor is a registered MBean. Accessible via JConsole, JMX clients, or Jolokia. Key operations: start/stop routes, view message counts, get exchange statistics.
• Camel Management API: Programmatic access to the same MBean data via context.getManagementStrategy(). Useful for embedding status checks in health endpoints.
• Micrometer: The camel-micrometer component registers Camel route/exchange metrics as Micrometer meters, which are scraped by Prometheus and displayed in Grafana. Add camel-micrometer-starter in Spring Boot for automatic registration.

# application.properties for Spring Boot metrics:
camel.metrics.enabled=true
management.endpoints.web.exposure.include=health,info,prometheus
management.metrics.export.prometheus.enabled=true

// Programmatic JMX access:
ManagedCamelContext mcc = context.adapt(ManagedCamelContext.class);
ManagedRouteMBean route = mcc.getManagedRoute("my-route-id", ManagedRouteMBean.class);
long count = route.getExchangesCompleted();
System.out.println("Completed: " + count);

In Spring Boot, adding spring-boot-starter-actuator + camel-micrometer-starter automatically creates Camel route metrics named camel.route.exchanges.completed, camel.route.exchanges.failed, and camel.exchange.event.notifier counters. JMX can be disabled with camel.springboot.jmx-enabled=false. For Kubernetes, combine with the Liveness/Readiness health checks from camel-health and the Actuator health endpoint.