Activity Logs Using Policy in IBM ACE

In this blog, we will learn about activity logs using policy in IBM ACE.

Activity Logs provide a summary of the high-level interactions that IBM App Connect Enterprise has with external resources, allowing you to better understand what your message flows are doing. They can be utilized to improve comprehension of the system as a whole and don’t require in-depth product knowledge.

It is possible to write Activity Logs to a circular file system. If we want to log activities continuously for a long time, we can set up file logging using the Activity Log policy.

Use these filtering features to customize log content to your specific needs. We can configure the size and number of log files and the criteria by which the log rotates from one file to the next. We can also determine the location and name of the log files.

The Activity Log policy allows you to set the following properties of the Activity Log file:

• Maximum number of files utilized for each log.
• Maximum size of log files (before the log rotates to the next file).
• Whether file logging is enabled, a fresh log file is created if the integration server is restarted and the maximum size is not reached.
• The oldest log file can exist before being rotated to the next file.
• Filters that determine the logs’ substance.
• Whether messages are prepared with inserts included in the message content.
• The intensity of the messages reported. 
• The log path and file name. 
• The scope of the policy (which integration servers it applies to)

For example, if the Number of log files property is set to 5, each integration server’s Activity Log may contain up to five files.

The Below screenshot contains the Application and policy which contains properties like File name, File size, number of log files and age of log files.

In the below screenshot we can see the generated log files.