- 0 minutes to read

Apache Camel, Logging, FAQ, Correlation, End-to-End Tracking, BPM Apache Camel, correlation, ApplicationInterchangeId, UUID, Exchange properties, JSON Log Event, end-to-end tracking, Business Process Model, BPM, process visualization, SLA monitoring, order processing, multi-route workflows Correlate transactions across multiple Apache Camel routes using ApplicationInterchangeId. Generate UUID in first route, pass through all subsequent routes. BPM visualizes complete end-to-end flow with color-coded status and SLA alerts.

How do I correlate transactions across multiple routes?

How do I correlate transactions across multiple Apache Camel routes?

Use ApplicationInterchangeId. When the first Camel route receives a transaction (e.g., REST API call creates Order), generate a unique ID (UUID.randomUUID().toString()) and store in Camel Exchange property: exchange.setProperty("ApplicationInterchangeId", correlationId).

All subsequent routes processing the same Order pass the same ApplicationInterchangeId in their [JSON Log Event][] payload. Nodinite groups all events by ApplicationInterchangeId—you see the complete end-to-end flow in one view.

Advanced: Configure [BPM][] (Business Process Model) with expected process steps (Route 1: Order Received → Route 2: Validate Inventory → Route 3: Charge Payment → Route 4: Ship Order). Nodinite visualizes the process with color-coded status (green = completed, yellow = in progress, red = failed). Alerts fire if expected steps don't complete within SLA (e.g., "Order should reach 'Ship Order' within 2 hours").

See all FAQs: [Troubleshooting Overview][]