Logs in PAM36015 minutes to read
PAM360 records different types of logs for various product-specific events. The log files contain error messages and other information that aids in analyzing and troubleshooting product-related issues. The event logs are stored locally in a text file under the directory path - <PAM360_Installation_Directory>\logs. 1. Steps to Configure Log Level SettingsFollow the below steps to configure and modify the log levels, as required:
2. Types of Logs in PAM360PAM360 offers a wide range of logs dedicated to cataloging detailed information about different types of operations in the product.
3. Log Retention and StorageBy default, the log files are stored in the path '<PAM360_Installation_Directory>\logs'. In general, the log files are used only to identify the root cause of errors and troubleshoot issues. The Audits feature in the product captures extensive log trails about the user and system-related operations and securely stores them in the PAM360 database, accessible from the PAM360 web interface. Therefore, the log files are safe to be deleted periodically. When you encounter an issue, it is recommended that you delete or rename the existing logs and reproduce the issue so that a fresh set of logs can be created—this will facilitate easy analysis and quicker troubleshooting. If you wish to move some of the main logs to a remote location for security reasons, you can do so by following the below steps:
The following files can be stored in remote locations:
All the primary log files are designed to be automatically rolled over as separate files with a number added at the end of the filename; therefore, you will find log files with filenames such as pam0, pam1, and pam2 in the directory. However, some logs such as AD_IMPORT_USERS_RESOURCES.txt and access_log.txt will not be rolled over and will continue logging in the same file. Since these logs take a long time to increase in size, it is safe to delete them if required. Note: Please ensure that you stop the PAM360 service before deleting any log files. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
[Webinar] Weave privileged access security into your org-wide ITSM workflows. Register now