Repository Audit Log Settings

The Laserfiche Server stores information about audited events in a set of binary log files in the AUDIT folder of the repository directory. To keep these files from becoming too large, by default the binary logs will roll over when they reach 50MB. You can customize your audit log settings, including location, maximum size, maximum age, and rollover directory.

Note: In general, smaller log files are better than very large ones. You cannot set the maximum log file size larger than 200MB.

To customize audit log settings

  1. Open the Laserfiche Administration Console.
  2. Expand the desired Laserfiche Server item.
  3. Select the desired Laserfiche repository.
  4. Log in as any user who has been granted the Manage Audit Settings privilege for the specified repository.
  5. Expand the Auditing node.
  6. Right-click the Settings node and select Properties.
  7. To change the location of the audit log data, type or browse to the new path in the Audit log path option.
  8. To create a new log file when the current log file reaches a certain maximum size, select Rollover log file when it reaches a maximum size and select a size in MB no larger than 200MB.
  9. To create a new log file when the current log file reaches a certain maximum age, select Rollover log file when it reaches a maximum age and select an age in days.
  10. To store old log files in a new location, type or browse to a new location in the Rollover directory option.
  11. To compress an audit log file when it is rolled over and archived, select Automatically compress rolled-over audit logs. The Compressed column in the Rollover Logs view will indicate whether the log has been compressed. These compressed logs will be stored in the location you defined in the previous step.

To customize audit log settings 

  1. Open the Laserfiche Web Administration Console.
  2. Select the desired Laserfiche Server.
  3. Select the desired Laserfiche repository.
  4. Log in as any user who has been granted the Manage Audit Settings privilege for the specified repository.
  5. Click Auditing.
  6. To change the location of the audit log data, type or browse to the new path in the Audit log path option.
  7. To create a new log file when the current log file reaches a certain maximum size, select Rollover log file when it reaches a maximum size and select a size in MB no larger than 200MB.
  8. To create a new log file when the current log file reaches a certain maximum age, select Rollover log file when it reaches a maximum age and select an age in days.
  9. To store old log files in a new location, type or browse to a new location in the Rollover directory option.
  10. To compress an audit log file when it is rolled over and archived, select Automatically compress rolled-over audit logs. The Compressed column in the Rollover Logs view will indicate whether the log has been compressed. These compressed logs will be stored in the location you defined in the previous step.

Note: If you are rolling over based on time, it is a good idea to roll over frequently if your repository is high-volume.

Note: Compressing an audit log does not remove data from the log.

Note: If you choose both a maximum size and a maximum age, the log file will roll over when the first criteria is reached. If rolling over based on size, the size of the uncompressed log is the one considered.