System Logs
Journey Manager (JM) Previously known as Transact Manager (TM). | 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:
- Event Log
- Error Log
- Error Log Trend
- Database Version Log
- T.Field Device Log | Removed in 21.11This feature was removed in 21.11.
- T.Field Sync Log | Removed in 21.11This feature was removed in 21.11.
- Import Log
- Audit Log
- Groovy Service Log
- Security Manager Log
- Apache Log
You can use System Event Publisher Overview to publish some logging events into various queues that are used by 3rd party tools, for example, Splunk.
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 entries will need to be tracked (a 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.