Hi You cannot expand those, it's hardcoded in the tracer implementation in Camel 3.x.
You can implement your own tracer via org.apache.camel.spi.Tracer and plug that into CamelContext. But an enhancement could be to allow to configure the TRACING_OUTPUT in the DefaultTracer so you can configure this. You are welcome to create a JIRA and try to implement this. On Mon, Nov 29, 2021 at 1:09 PM Vyacheslav Boyko <mail4...@gmail.com> wrote: > > Hi! > > 14:07:29.172 [Test worker] INFO org.apache.camel.Tracing - *--> > [route1 ] [from[direct://start] ] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: ... > 14:07:29.176 [Test worker] INFO org.apache.camel.Tracing - [route1 > ] [marshal[org.apache.camel.model.da] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: ... > 14:07:29.274 [Test worker] INFO org.apache.camel.Tracing - [route1 > ] [direct://payment-details ] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: ... > 14:07:29.276 [Test worker] INFO org.apache.camel.Tracing - ---> > [rms-payment-] [from[direct://payment-details] ] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: byte[], ... > 14:07:29.276 [Test worker] INFO org.apache.camel.Tracing - > [rms-payment-] [setProperty[CamelKafkaManualCommi] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: ... > 14:07:29.288 [Test worker] INFO org.apache.camel.Tracing - > [rms-payment-] [removeHeader[CamelKafkaManualComm] Exchange[Id: > E2E34A8700E4EE3-0000000000000000, BodyType: ... > > I see here are blocks of datum: > > 1) time > 2) thread ID > 3) logger name > 4) in/out/continue (*-->, -->) > 5) route id > 6) route definition / endpoint uri > 7) the very log > > Is there any possibility to expand route id and route definition blocks? > > They contain very small portion of info needed. > > -- > Vyacheslav Boyko > mailto:mail4...@gmail.com > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
