Many container deployment solutions provide the ability to view the console logs STDOUT and STDERROR for a container. When running a Docker image of Integration Server in a Docker container, Integration Server writes the server log to the console as well as to the server.log file. Server log messages written to STDOUT include the identifier “ISSERVER” to help differentiate server log messages from other messages written to the console.

Docker includes logging drivers to help obtain information from running containers. If you use the json-file logging driver or journald logging driver with your Docker solution, the driver captures information written to STDOUT and writes it to a file. Running the docker logs command displays the contents of that file. The size of the file used for logging can grow. You may want to consider using logging driver options to limit the size of the file and prevent disk overflow issues.

For example, The size of the JSON file used for logging can grow indefinitely. That is, by default, there is no maximum limit to the size of this file. If your Docker solution uses the json-file logging driver, you may want to consider limiting the size of the JSON file by rotating the JSON log files.

To specify a size limit for the JSON log file or any other options for the json-file logging driver, supply one or more of the supported json-file logging options in the docker run command. For example, the following starts a Docker container named IS_1 using the is:microPkg image. The container can have a maximum of 4 log files with maximum size of 25MB each:

For information about the json-file logging driver or any other logging driver included with Docker, consult the Docker documentation.