Implementing rollover conditions for vds_server_access logs when default folder location is changed.

Product: FID

Version: v7.2.x / v7.3.x / v7.4.x

Question:

The vds_server_access logs are not removed once the rollover conditions are met when the default folder location is changed to a custom folder location.

Example:

Answer:

The access.log.file.archive.scan.folder parameter is used to scan the folder and remove the archived logs once the rollover conditions are met. It is crucial to properly set this folder location in order for VDS to automatically remove the logs.

Unlike vds_server logs, which have the "server.log.file.archive.scan.folder" parameter available in Advanced Settings, the vds_server_access logs do not have this option in the UI.

To fix the cleanup issue, you can update the following parameter by editing it directly in ZooKeeper:

NOTE: If you don’t see Zookeeper, switch to Expert Mode. To do this, select the arrow next to the logged-in user, then select Expert Mode. FID will reload, and the ZooKeeper tab will be displayed.

For versions v7.4.x and later:

• Update the ZooKeeper node at /radiantone/v2/<cluster_name>/config/logging/log4j2-vds.json.

For versions v7.3.x and earlier:

• Update the ZooKeeper node at /radiantone/v1/<cluster_name>/config/logging/log4j2-vds.json.

The part of the configuration that needs to be updated with the new log folder location is "${rli:logging.root}/ and be updated with the new folder location"c:/test_logs/ :

EXAMPLE:

DEFAULT

Updated Folder

This ensures that the logs will be properly cleaned up from the custom folder location after the rollover conditions are met.