The server maintains logs for auditing and troubleshooting.
The audit log shows information about who accessed the server and what changes each user made.
The diagnostics log shows a table of information about actions on the server. This table shows which user ran an action, when that action was run and what part of the server API was used.
Server output log#
The server output log shows information about all the actions that are performed on the server.
- Viewing logs
You can view logs from the Settings > System page.
- Changing the server output log contents
The server stores its log by using Apache Log4j version 1.2.16. You can edit the Log4j settings to change the format of the log and the information that is added to the log.
- Creating a rotating audit log file
You can create rotating audit log file at a regular interval, such as every day.
- Increasing the size of the log file
Log data contains information that is written by components within the product. The log provides a snapshot of the flow and transfer of information between components. The log data includes the time frames for when problem occurred on the server, client, and agent. Because the log file holds a limited amount of data, data related to a problem can be overwritten.
- Determining the Java heap memory size
The Java heap is memory that contains objects used by Java programs. It contains objects that are currently in use, objects that are no longer needed, and free memory. Objects that are no longer needed are freed by the garbage collection process. The JVM heap size determines how often to run garbage collection and how long the garbage collection runs.
Parent topic: Troubleshooting and support