The Container log file contains information related to the operation of the Atom, Molecule, or Cloud runtime itself. The log is intended for runtime owners to monitor and troubleshoot their runtimes.
The Contain log includes information about the runtime’s activities such as:
- Atom status (e.g. startup, shutdown, restart)
- Unexpected runtime errors
- Listener server startup/shutdown and listener service registrations
- Processing of MDN messages
- Purging of temporary data
- Communication with the AtomSphere platform
The Container logs contain information related to Atom-level errors. This information is very important when it comes to ad hoc troubleshooting of issues/errors encountered with your integrations. It is also helpful information to share with Dell Boomi Technical support when opening a case via the Support portal.
As a best practice, monitoring the Container logs for errors and warnings is an important part of a comprehensive operational monitoring strategy. See Operational Monitoring Best Practices for Atom, Molecule, and Atom Cloud Runtimes.
Viewing the Log
The logs can be accessed by either the AtomSphere UI or the local runtime directory. If you are using a clustered Molecule or Atom Cloud there will be a separate container log created for each node. Molecule container logs can be accessed the same way as Atom container logs.
Note: You can only download the Container logs if your account owns the local Atom, Molecule, or Atom cloud. For example, you cannot download the Container logs for the Dell Boomi Atom Cloud that is managed by Dell Boomi. To obtain runtime information specific to your tenant, please contact Dell Boomi Support.
- From the AtomSphere UI:
- The logs can be downloaded through the AtomSphere UI from Manage > Atom Management > select Atom > Logs > Atom Logs. See Downloading an Atom, Molecule or Cloud’s log files for more information.
- From the local runtime directory:
- Log directory: ../<atom_install_dir>/logs
- File name for Atoms:<yyyy_MM_dd>.container.log
- File name for Molecules and Atom Clouds: <yyyy_MM_dd>.container.<node_IP_address>.log
The Atom Container logs are purged according to the runtime's purge schedule.
Log Structure and Columns
There will be one message per line in the logs. An error message stacktrace would be the only type of log entry you will see that contains multiple lines.
The timestamp of the log entries will correspond with the local timezone where the Atom is installed.
Feb 28, 2017 12:08:51 PM EST INFO [com.boomi.container.core.StatusReporter start] Starting Status Reporter
Timestamp (Local Timezone where Atom is installed)
Feb 28, 2017 12:08:51 PM EST
Java Library and Class
Starting Status Reporter
There are four different log levels you will see in the Container logs.
- Info - Indicate Tasks being performed by the Atom
- Fine - Indicate that the Atom is operating as expected
- Warning - Indicates there was some type of issue. Warning log levels may be temporary or may lead to a Severe log level.
- Severe - Indicates there is an issue that needs to be addressed. Severe log level entries will usually be associated with an error message and a stack trace of the error message will usually be included.
Example of Severe log level with partial stacktrace:
Feb 27, 2017 3:50:46 PM EST SEVERE [com.boomi.connector.generic.GenericConnectorBrowseAction browse] Unable to browse connector
com.boomi.connector.api.ConnectorException: Unknown failure: java.io.IOException: Unable to retrieve wsdl0.
at com.boomi.connector.msdcrm.online.CRMOnlineConnector.createBrowser(CRMOnlineConnector.java:33) at com.boomi.connector.generic.GenericConnectorBrowseAction.createBrowser(GenericConnectorBrowseAction.java:230)
Tips for Using the Container Logs
The logs are primarily used for troubleshooting issues and determining the root cause of issues with the Atom and with your integrations. The logs give you the ability to examine what is happening during runtime both before and after an issue is recognized. The container logs can also be used in conjunction with third party monitoring tools such as Splunk to help pinpoint an issue and resolve as quickly as possible.
When troubleshooting issues using the container logs you will be focusing primarily on identifying errors that are logged as Severe. If you have a lot running on your Atom the logs can sometimes be very large. You can quickly search through the logs by using the Find tool (Ctrl+F) and search for Severe or the error message itself if you already know what the error is.
Making sure you are looking at the correct time of an issue/error message is important when using the container logs. The container log timestamp will be from timezone where the Atom is installed. Process reporting in the Atomsphere is displayed in your machine/computers local timezone. If you have an Atom installed on a server that is using EST timezone and you are logged into AtomSphere in PST timezone you will have to convert any errors you see in Process Reporting to EST in order to find them in the Container logs.
Note that not all errors or warnings require action. Some errors can be ignored and will resolve themselves, most of the time. An example of such error message can be seen in this article: java.io.IOException: Unable to post messages: Service Unavailable (503) Connection threshold has been reached
You can also enable Debug Mode on an Atom which will include more information in the container logs for troubleshooting purposes. Debug mode should only be enabled to troubleshoot an issue and should be disabled when not necessary. Leaving debug mode on during general atom operation could impact the performance of the atom and also create very large log files potentially using up needed disk space.
See How to enable debug mode in an atom for more information.