Event Lifecycle Logging
Event lifecycle logging, also called trace logging, uses a trace logger to create detailed logs describing the flow of a message (event) as its published by a Universal Messaging client, routed through Universal Messaging, and as its received by the subscribing Universal Messaging client.
Note:Integration Server functions as a Universal Messaging client when it publishes messages to Universal Messaging and when it receives messages from Universal Messaging, typically via triggers.
When event lifecycle logging is enabled it captures event activity on the Universal Messaging server and Integration Server (a Universal Messaging client). The event life cycle logs from Integration Server and Universal Messaging server do not provide the exact same information
. The event lifecycle logs on Integration Server record client activities. Whereas the event lifecycle logs on Universal Messaging record messaging server activities. Together, the logs provide a detailed picture of how events move between the products. This can be useful when you are looking for a missing message. If you know the tag (UUID) of the message, you can examine the logs to see at which point the message was lost
. Or, if message processing is slow, you can use the event lifecycle logs to see where the processing delay occurs.
When you configure event lifecycle logging on Integration Server, you determine:
Trace level. The logging level which can be Trace, Info, or Off.
Trace stores. The message stores for which
Integration Server performs event life cycle logging. The message stores are channels or queues to which
Integration Server sends messages to or receives messages from. You can configure
Integration Server to perform event lifecycle logging for all message stores with which
Integration Server interacts.
Trace log size. The maximum size of the event lifecycle log for each message store. When the event lifecycle log reaches this size,
Integration Server creates an archive of the log (.zip) and starts a new lifecycle log for the store.
Trace folder size. The maximum size of all event lifecycle logs combined.
When the total size of all event lifecycle logs and archives exceeds this value,
Integration Server deletes the oldest archive (*.zip) files.
If the logging level is set to Trace or Info, when Integration Server sends or receives messages to a queue or channel in the trace store list, Integration Server writes lifecycle log entries to the log file for the store. Integration Server uses a separate lifecycle log for each store. All lifecycle logs are located in the following directory:
Integration Server_directory /instances/instanceName/logs/umEventLifecycle
For example:
Integration Server_directory /instances/
instanceName/logs/umEventlifecycle/wm/is/my/doc
Where wm/is/my/doc is the channel that corresponds to a publishable doucmetn type named my:doc
Integration Server_directory /instances/
instanceName/logs/umEventlifecycle/queue1
Below is an example of log entires for event lifecycle logging.
[2021-06-25 16:44:00,809][TRACE][Adding durable asynchronous subscriber. windowSize=-1, selector=null, autoAck=false, durableInfo={durableName=J_jRQtEolDEurgAVIwwwADXaZQs_##serialtest__trig, durableType=Named, nameId=11, selector=}, Conn={SSID:544f00000000,Local:127.0.0.1:59908,URL:nsp://127.0.0.1:9000}][nChannelImpl][Server Thread Pool - serialtest:trig]
[2021-06-25 16:44:00,810][INFO][Asynchronous durable subscriber successfully added.][nChannelImpl][Server Thread Pool - serialtest:trig]
[2021-06-25 18:20:56,388][INFO][Publish request. nPublished={EID=0, tag=wm:fe1b2bf0-d60b-11eb-8963-000000000001}, Conn={SSID:544d00000000,Local:127.0.0.1:59384,URL:nsp://127.0.0.1:9000}][nTransaction][HTTP Handler 127.0.0.1]
[2021-06-25 18:20:56,390][INFO][Publishing & committing transaction. transactionId=92689689214976, ttl=1000, publishTime=-1, Conn={SSID:544d00000000,Local:127.0.0.1:59384,URL:nsp://127.0.0.1:9000}, eventsCount=1, events={EID=0, tag=wm:fe1b2bf0-d60b-11eb-8963-000000000001}][nTransaction][HTTP Handler 127.0.0.1]
[2021-06-25 18:20:56,393][TRACE][Publishing response to client. nConsumeEvent={EID=147, tag=wm:fe1b2bf0-d60b-11eb-8963-000000000001, redelivery=0}][nClientChannelList][UM-Connection-Reader:3 Active]
[2021-06-25 18:20:56,393][TRACE][Received event on client. nConsumeEvent={EID=147, tag=wm:fe1b2bf0-d60b-11eb-8963-000000000001, redelivery=0}][nClientChannelList][UM-Connection-Reader:3 Active]
Note:
In event lifeyclce logs the tag is synonymous with UUID.