Custom Logs
The custom log provides important information that you need to monitor and correct problems that occurred during the service execution. IBM® webMethods Cloud Container offers the capability to download these custom logs through the Monitor > Logs page.
In this case, the customer creates a custom log file for each service. The consequent execution of the same service will append custom log entries to the same log file. Customers will also configure rotating the custom log file in a periodic manner, either by day or by size. Upon rotation, the rolled-over logs are renamed and made available through the Monitor > Logs page.
Before You Begin
- Make sure that the custom log file resides in the following directory: /opt/softwareag/IntegrationServer/instances/default/logs/custom_pkg_logs/<file_name>.log. You cannot change the location of the log file.
-
Ensure that there is the file access permission to modify the parameters set for directories in the fileAccessControl.cnf configuration file.
-
If you have any older versions of Log4j installed, you must update to log4j 2.17.1 or a higher version.
-
As a best practice, the logs must be rotated periodically based on the size or on the date. It is recommended to rotate the custom log when the custom log file size reaches 50 MB size or at midnight, whichever occurs first.
How to Identify Custom Log Entries?
Upon rotation, you can view the custom log file through the Monitoring > Logs page of IBM webMethods Cloud Container. Use the following format to identify the custom log entries:
<file-name>.log.<time_stamp>.yyyymmdd.time_stamp.zip
Downloading the Custom Log
To download the custom log details, click 
under
Actions.