Enhanced logging for messaging is a configurable feature that instructs Integration Server to write detailed log entries when sending or receiving and processing messages. The detailed logging, referred to as enhanced logging, makes it possible to track an individual message across your Integration Servers from the time the message is published through the time a trigger receives, processes, and acknowledges the message.

Each log message presents information about the message progress in a consistent way, making it possible to track the progress of the message through Integration Server. Most importantly, whenever possible, enhanced logging entries include a unique identifier for the message being published or consumed. Being able to track individual messages can help in debugging issues in your messaging solution.

Integration Server provides many configuration options for the enhanced messaging logging. These options can help focus the log entries on particular areas of your messaging implementation as well as limit the impact of enhanced logging on performance. For example, you configure enhanced logging for an individual messaging connection alias and not the entire Integration Server. For each alias you can specify whether Integration Server generates additional logging for all message consumers and/or producers or just specific message consumers and/or producers. You can also specify whether or not the enhanced messaging logging is verbose by setting a logging level.

Enhanced logging is available for JMS messaging and webMethods messaging only. It is not available for MQTT messaging.