...
And in Camel 2.2 you can use the log
DSL which allows you to use Simple language to construct a dynamic message which gets logged.
For example you can do
Code Block |
---|
from("direct:start").log("Processing ${id}").to("bean:foo");
|
...
Tip |
---|
title | Logging message body with streamed messages |
---|
|
If the message body is stream based, then logging the message body, may cause the message body to be empty afterwards. See this FAQ. For streamed messages you can use Stream Cachingcaching to allow logging the message body and be able to read the message body afterwards again. |
The log DSL have overloaded methods to set the logging level and/or name as well.
Code Block |
---|
from("direct:start").log(LoggingLevel.DEBUG, "Processing ${id}").to("bean:foo");
|
and to set a logger name
Code Block |
---|
from("direct:start").log(LoggingLevel.DEBUG, "com.mycompany.MyCoolRoute", "Processing ${id}").to("bean:foo");
|
Since Camel 2.12.4/2.13.1 the logger instance may be used as well:
Code Block |
---|
|
from("direct:start").log(LoggingLeven.DEBUG, org.slf4j.LoggerFactory.getLogger("com.mycompany.mylogger"), "Processing ${id}").to("bean:foo"); |
For example you can use this to log the file name being processed if you consume files.
Code Block |
---|
from("file://target/files").log(LoggingLevel.DEBUG, "Processing file ${file:name}").to("bean:foo");
|
...
In Spring DSL its also easy to use log DSL as shown below:
Code Block |
---|
|
<route id="foo">
<from uri="direct:foo"/>
<log message="Got ${body}"/>
<to uri="mock:foo"/>
</route>
|
The log tag has attributes to set the message
, loggingLevel
and logName
. For example:
Code Block |
---|
|
<route id="baz">
<from uri="direct:baz"/>
<log message="Me Got ${body}" loggingLevel="FATAL" logName="com.mycompany.MyCoolRoute"/>
<to uri="mock:baz"/>
</route>
|
Since Camel 2.12.4/2.13.1 it is possible to reference logger instance. For example:
Code Block |
---|
|
<bean id="myLogger" class="org.slf4j.LoggerFactory" factory-method="getLogger" xmlns="http://www.springframework.org/schema/beans">
<constructor-arg value="com.mycompany.mylogger" />
</bean>
<route id="moo" xmlns="http://camel.apache.org/schema/spring">
<from uri="direct:moo"/>
<log message="Me Got ${body}" loggingLevel="INFO loggerRef="myLogger"/>
<to uri="mock:baz"/>
</route>
|
...
You can specify a marker name in the DSL
Code Block |
---|
|
<route id="baz">
<from uri="direct:baz"/>
<log message="Me Got ${body}" loggingLevel="FATAL" logName="com.mycompany.MyCoolRoute" marker="myMarker"/>
<to uri="mock:baz"/>
</route>
|
Using log DSL in OSGi
Improvement as of Camel 2.12.4/2.13.1
When using log DSL inside OSGi (e.g., in Karaf), the underlying logging mechanisms are provided by PAX logging. It searches for a bundle which invokes org.slf4j.LoggerFactory.getLogger()
method and associates the bundle with the logger instance. Passing only logger name to log DSL results in associating camel-core
bundle with the logger instance created.
In some scenarios it is required that the bundle associated with logger should be the bundle which contains route definition. This is possible using provided logger instance both for Java DSL and Spring DSL (see the examples above).
Include Page |
---|
| Using This Pattern |
---|
| Using This Pattern |
---|
|