System Logs

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |  v5.1 & Higher This feature is related to v5.1 and higher.

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 maintains the following logs, which reside both on the file system and in the database:

• Event Log
• Error Log
• Error Log Trend
• Database Version Log
• T.Field Device Log
• T.Field Sync Log
• Import Log
• Audit Log
• Groovy Service Log
• Apache Log

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

Dos:

• Do choose the correct log file for the scenario
• Do make your log entries meaningful
• Do add a correlation key if multiple log entires will need to be tracked (submission key is often sufficient)
• Do use try and catch blocks for known issues

Don'ts:

• Don't log any Personally Identifying (PI) data - if you really must in order to write a peice of code then make a note or create a story to remove it later
• Don't log any Personally Identifying (PI) data - did I mention that already? Oh, well it is really important!
• Don't be overly chatty

Next, learn more about the Event Log.