System Logs

   Journey Manager (JM) The transaction engine for the platform.  |    System Manager / DevOps  |   21.11 This feature was updated in 21.11.

Manager captures a wide range of system and service run-time information and stores it in different log files. It provides a convenient interface for viewing this information, making it easier to troubleshoot diverse production problems.

Manager creates and maintains the following logs, which reside both on the file system and in the database:

You can use Topics to publish some logging events into various queues that are used by 3rd party tools, for example, Splunk.

A good way to detect issues is to keep an eye on the logs provided by Manager. Inspect the error log and the event log regularly to be alerted to irregularities and problems of all sorts. Make sure you look into issues that you do not fully understand, using additional logs such as the submission and request log to track users' activities, the audit log to track changes made by administrators, the system health log to track vital system statistics or the log files maintained by the application server.

If you have multiple administrators set up in Manager, the audit log should also be monitored to make sure no unintended or harmful changes have been made.

When you log various events into a log file, there are a few recommended practices, as shown below:


  • Do choose the correct log file for your scenario, for example, error log to keep track of all relevant to your application
  • Do make your log entries meaningful
  • Do add a correlation key to track multiple log entries. In some cases, a submission key is often sufficient
  • Do use try-catch blocks for known issues


Next, learn more about the Event Log.