Logging Configuration for idenprotect Active Directory Agent
If you have not made any configuration changes yet, please see How to make configuration changes
Introduction
As with all of our applications, throughout the normal operation of the idenprotect Active Directory Agent, logs will be created in the file system. The majority of these logs are to audit manual and automated processes but it can also act as a red flag if anything goes wrong.
The AD Agent logs are currently not integrated into the idenprotect Core Platform log views. The logs can be manually viewed by visiting the Log File Location (see below).
The logging.properties file must exist for the application to run, if it has not been created during the installation process, please go to the bottom of the page where you will find the contents for an example logging.properties file.
Configuring the Logging
These properties can be found in:
- Server file system in
/etc/idenprotect/adsync/logging.properties
| Parameter in Properties File | Description |
|---|---|
logging.file
|
Log file location (default = /var/log/idenprotect/adsync/adsync.log) |
logging.filePattern
|
Log file rolling parameter (use yyyy-MM-dd-HH-mm for minutes) and location to save rolled logs (default = /var/log/idenprotect/adsync/adsync.%d{yyyy-MM-dd}.%i.log) |
logging.maxFileSize
|
Log file maximum size until rolling (default = 30MB) |
logging.maxHistory
|
Log file maximum amount of days to store data (default = 30) |
Example logging.properties file
#Log file location
logging.file=/var/log/idenprotect/adsync/adsync.log
#Log file rolling parameter (use yyyy-MM-dd-HH-mm for minutes) and location to save rolled logs
logging.filePattern=/var/log/idenprotect/adsync/adsync.%d{yyyy-MM-dd}.%i.log
#Log file maximum size until rolling
logging.maxFileSize=30MB
#Log file maximum amount of days to store data
logging.maxHistory=30
