Re point 2. After looking at messages as they flow through routes am I right in saying that the breadcrumbid doesn't ever change once set? If so then the breadcrumbid would be a "MessageLifecycleId"........
I can't find any description of how the breadcrumbid is determined. I originally thought it would change every new exchange and provide breadcrumbs back to the original msg id... On Wed, 4 Mar 2020 at 10:13, nomit babraa <h.bab...@sheffield.ac.uk> wrote: > > Hi > > I've read about the Tracer EIP > (https://camel.apache.org/manual/latest/tracer.html) and also the MDC > options (https://people.apache.org/~dkulp/camel/mdc-logging.html) and > was wondering 2 things please: > > 1) Can you add other data to the MDC like another header or property? > How is this done? Even the excellent Camel in Action book doesn't seem > to have a section on MDC. > > 2) Both provide a way to track and trace messages to plot/correlate > their journeys but this blog > (https://jack-vanlightly.com/blog/2017/6/11/improving-reliability-and-incident-response-via-a-message-lifecycle) > makes an interesting point about a "MessageLifecycleId" > > "For this purpose in our system we add a MessageLifecycleId message > header to all messages. Every time a message is sent, even when a > message is sent for retries, it gets a new MessageId, but we always > transfer over the MessageLifecycleId header. No matter how many times > a message bounces around the system, it keeps its MessageLifecycleId." > Thios > > I was wondering if there is OOTB support for such a thing? > > Thanks > n -- Nomit Babraa Split Working Pattern: Student Lifecycle Project (SLP) and IT Services on alternate weeks (Please check my calendar) Tel: 0114 222 1162
