messageLoggingStrategy
Strategy for describing how a processor’s message is logged on the server.
Note that logging the full message/payload is only available in local development. It is also recommended to use the Utilihive SDK’s tracing feature to debug messages instead of relying on a message logging strategy.
If you intend to store payloads in a production environment, you must implement an archiving strategy. Proper archiving is the only way to achieve performant storage of payloads. See the payloadArchivingStrategy sub-builder and the archiveLookup processor for more details.
| Enabling payload logging in an environment can cause significant performance and stability issues, especially when logging large payloads. Use this feature only in local development environments or with extreme caution in production. |
Properties
| Name | Summary |
|---|---|
|
Adds a name to a list of message exchange properties to log. Wildcard |
|
Whether to log the description associated with the message. |
|
Whether to log the full message (i.e., the payload). This feature requires the server config: |