The functionality described in this article is available in meshIQ Manage versions 12.1 and greater.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.  

Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier

Version 12.x and Later

The Activity Logs feature for Message Flows in IIB/ACE provides visibility into runtime flow activity, including node-level events, thread behavior, waiting conditions, and diagnostic information. These logs help developers and administrators understand what is happening inside a running message flow, making it easier to troubleshoot processing delays, node behavior, and operational issues.

View Message Flow Activity Logs

To view activity logs for a message flow:

1. In the Message Flow widget, select the message flow you want to inspect.

2. From the Selected menu, click Activity Logs.
   

3. The ACE Message Flow Activity Logs dialog opens.
   

4. A table displays detailed activity log entries for the selected message flow, including:

   • BIP Number – The message code identifying the event type.

   • Timestamp – Time the event occurred.

   • Tag Value  – The name of the operation or action performed.

   • Tag Name – Indicates the flow node or component involved.

   • Source – Component that generated the log entry.

   • Thread Id – Server thread that processed the event.

   • Thread Sequence Number – Order of events within the same thread.

   • Message – Brief description of the event.

   • Detailed Message – Expanded explanation for troubleshooting.

5. Use the filter fields at the top of each column to refine the results as needed.

6. You can scroll through the logs and navigate between pages using the controls at the bottom of the window.

_________________________________________________________________________________________________________________

Version 11.3 and Earlier

The Activity Logs feature for Message Flows in IIB/ACE provides visibility into runtime flow activity, including node-level events, thread behavior, waiting conditions, and diagnostic information. These logs help developers and administrators understand what is happening inside a running message flow, making it easier to troubleshoot processing delays, node behavior, and operational issues.

View Message Flow Activity Logs

To view activity logs for a message flow:

1. In the Message Flow viewlet, select the message flow you want to inspect.

2. From the Selected menu, click Activity Logs.
   

3. The ACE Message Flow Activity Logs window opens.
   

4. A table displays detailed activity log entries for the selected message flow, including:

   • BIP Number – The message code identifying the event type.

   • Timestamp – Time the event occurred.

   • Tag / Tag Name – Indicates the flow node or component involved.

   • Source – Component that generated the log entry.

   • Thread ID – Server thread that processed the event.

   • Thread Sequence Number – Order of events within the same thread.

   • Message – Brief description of the event.

   • Detailed Message – Expanded explanation for troubleshooting.

5. Use the filter fields at the top of each column to refine the results as needed.

6. You can scroll through the logs and navigate between pages using the controls at the bottom of the window.
   Click Clear Filters to reset all filters.