Skip to content

Log Mediator

The Log mediator is used to log mediated messages. For more information on logging, see Monitoring Logs.


The Log mediator is a conditionally content aware mediator.


The log token refers to a <log> element, which may be used to log messages being mediated.

<log [level="string"] [separator="string"]>
   <property name="string" (value="literal" | expression="[XPath|json-eval(JSON Path)]")/>*


The general parameters available to configure the Log mediator are as follows.

Parameter Name Description
Log Category

This parameter is used to specify the log category. Possible values are as follows. Following log levels correspond to the ESB profile service level logs.

  • TRACE - This designates fine-grained informational events than the DEBUG.
  • DEBUG - This designates fine-grained informational events that are most useful to debug an application.
  • INFO - This designates informational messages that highlight the progress of the application at coarse-grained level.
  • WARN - This designates potentially harmful situations.
  • ERROR - This designates error events that might still allow the application to continue running.
  • FATAL - This designate s very severe error events that will presumably lead the application to abort.

Log Level

This parameter is used to specify the log level. The possible values are as follows.

  • Full : If this is selected, all the standard headers logged at the Simple level as well as the full payload of the message will be logged. This log level causes the message content to be parsed and hence incurs a performance overhead.
  • Simple : If this is selected, the standard headers (i.e. To , From , WSAction , SOAPAction , ReplyTo , and MessageID ) will be logged.
  • Headers : If this is selected, all the SOAP header blocks are logged.
  • Custom : If this is selected, only the properties added to the Log mediator configuration will be logged.

The properties included in the Log mediator configuration will be logged regardless of the log level selected.

Log Separator

This parameter is used to specify a value to be used in the log to separate attributes. The , comma is default.

Use only the Source View to add a tab (i.e., by defining the separator="&#x9;" parameter in the syntax) or a new line (i.e., by defining the separator="&#xA;" parameter in the syntax ) as the Log Separator , since the Design View does not support this.

The parameters available to configure a property are as follows:

Parameter Name Description
Property Name The name of the property to be logged.
Property Value

The possible values for this parameter are as follows:

  • Value: If this is selected, a static value would be considered as the property value and this value should be entered in the Value/Expression parameter.
  • Expression: If this is selected, the property value will be determined during mediation by evaluating an expression. This expression should be entered in the Value/Expression parameter.


This parameter is used to enter a status value as the property value, or to enter an expression to evaluate the property value based on the what you entered for the Property Value parameter. When specifying a JSONPath, use the format json-eval(<JSON_PATH>) , such as json-eval(getQuote.request.symbol).

Action This parameter allows the property to be deleted.


Using Full log

In this example, everything is logged including the complete SOAP message.

<log level="full" xmlns=""/>

Using Custom logs

In this example, the log level is custom . A property with an XPath expression which is used to get a stock price from a message is included. This results in logging the stock, price which is a dynamic value.

<log level="custom" xmlns="">
    <property name="text"
              expression="fn:concat('Stock price - ',get-property('stock_price'))"/>