...
Option | Default | Description |
|---|---|---|
breadCrumbLength | 0 | Camel 1.5.1: Fixed length of the bread crumb. 0 = no fixed length. Setting a value to e.g. 80 allows the tracer logs to be aligned for easier reading. |
nodeLength | 0 | Camel 1.5.1: Fixed length of the node. 0 = no fixed length. Setting a value to e.g. 40 allows the tracer logs to be aligned for easier reading. |
showBreadCrumb | true | Outputs the unique unit of work for the exchange. To be used for correlation so you can identify the same exchange. |
showNode | true | The destination node In Camel 1.x its the destination node. In Camel 2.0 its both the previous and destination node, so you can see from -> to. |
showExchangeId | false | To output the unique exchange id. Currently the breadcrumb is sufficient. |
showShortExchangeId | false | Camel 1.5.1: To output the unique exchange id in short form, without the hostname. |
showProperties | true | Output the exchange properties |
showHeaders | true | Output the in message headers |
showBodyType | true | Output the in body Java type |
showBody | true | Output the in body |
showOutBodyType | false | Camel 2.0: Output the out body Java type |
showOutBody | false | Camel 2.0: Output the out body |
showExchangePattern | true | Camel 1.5: Output the exchange pattern |
showException | true | Camel 1.5: Output the exception if the exchange has failed |
...
| Wiki Markup |
|---|
{{ID-claus-acer/3690-1214458315718/2-0}} is the breadcrumb with the unique correlation id.
{{node3}} is the id of the node in the route path. Is always shown.
{{To\[mock:a\]}} is the destination node.
{{InOnly}} is the exchange pattern. Is always shown.
Then the rest is properties, headers and the body. |
Showing from and to
In Camel 2.0 the trace log will output both the from and to so you can see where the Exchange came from, such as:
| Code Block |
|---|
>>> direct:start --> process(MyProcessor)
>>> process(MyProcessor) --> to(mock:a)
>>> to(mock:a) --> to(mock:b)
|
Enabling
To enable tracer from the main run
...