davsclaus opened a new pull request, #23765: URL: https://github.com/apache/camel/pull/23765
## Summary - Capture the breadcrumb ID (`CamelBreadcrumbId` header) in `BacklogTracerEventMessage` and use it to correlate message history across broker boundaries - When exchanges pass through Kafka, SEDA, JMS, etc., each consumer creates a new independent exchange — the breadcrumb ID links them so the history tab shows the full end-to-end flow - Falls back to exchange ID / correlation ID matching when breadcrumb is not set ## Changes - **`BacklogTracerEventMessage`** (API): Added `getBreadcrumbId()` method (`@since 4.21`) - **`DefaultBacklogTracerEventMessage`**: Added `breadcrumbId` field, constructor parameter, getter, and JSON serialization - **`BacklogTracer.traceEvent()`**: Updated correlation logic to match by breadcrumb ID first, falling back to exchange/correlation ID when breadcrumb is null - **`BacklogTracer.traceNode()`**: Read breadcrumb ID from exchange header - **`CamelInternalProcessor`**: Updated all 6 constructor call sites to pass breadcrumb ID - **`DefaultBacklogDebugger`**: Updated all 4 constructor call sites to pass breadcrumb ID ## Test plan - [x] `BacklogTracer*` tests pass in `camel-core` - [x] `BacklogTracerMessageHistoryTest` passes in `camel-management` - [x] All `BacklogTracer*` tests pass in `camel-management` - [ ] Manual test with multi-route topology (Kafka/SEDA) to verify cross-broker history correlation _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
