Logs
This section provides information related to logs.
Log and Trace Model
PPM produces several logs for troubleshooting and audit. In addition, the history of changes to existing objects (project, request, and so on) are stored in the database as history. This information remains as long as the object itself is not deleted.
Recommendations:
- Pay attention to the log level and do not leave the level at Debug except for troubleshooting.
- Pay attention to log rotation.
- Restrict access to the log directory.
- If logs archiving is needed, create your own archiving policy.
Log and Trace Security Administration and Features
Sensitive data is kept on log files. PPM provides applicative logs that can report all system events according to log level. It is the user’s responsibility not to insert unprotected sensitive data to regular PPM entity fields.
The data provided in log files depends on the log level. For details, see Logging parameters.
FAQ
Question
Does PPM audit access to need-to-know information and key application events?
Answer
Yes, through the application log files.
Question
Does PPM display the user’s time and date of the last change in data content?
Answer
Yes, for entity fields marked as history enabled.
Question
Does PPM support the creation of transaction logs for access and changes to the data?
Answer
The information can be found in the application logs based on the log level. The data provided in log files depends on the log level. For details, see Logging parameters.

