audit-max-records
Section: history-log
Default Value: 50000
Valid Values: Any positive integer
Changes Take Effect: Immediately
Specifies the maximum number of records that can be stored in the database. When the maximum number of records is reached, Master Configuration Server will delete the older records while adding new records. Genesys recommends not to set the value above 100000 for performance reasons. Configuration Server cleans up the history records based on this option every 30 minutes.
audit-expiration
Section: history-log
Default Value: 365
Valid Values: Any positive integer
Changes Take Effect: Immediately
Specifies the number of days of records to retain in the database. For example, if the value is set to 30, the records of the last 30 days will be kept in the database and older records will be deleted. The maximum value for this option is 365. Configuration Server cleans up the history records based on this option every 30 minutes.
Note: The value of this option must always be greater than expiration.
8.5.101.24
Configuration Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 08/10/18 | General | X | X | X | X |
Contents
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Starting with this release, Configuration Server can utilize User Principal Name (UPN) usernames for Kerberos external authentication.
- Configuration Server now uses extended retention policies for audit records that are stored in the database. Audit records of a maximum of 100 thousand entries can be stored by Configuration Server for up to 1 year. Configuration Server cleans up the history records every 30 minutes. The configuration options audit-expiration and audit-max-records are introduced for this feature.
Resolved Issues
This release contains no resolved issues.
Upgrade Notes
No special procedure is required to upgrade to release 8.5.101.24.