Adobe Connect Server Log Retention

This article applies to on-premise deployments of Adobe Connect and is intended for Adobe Connect server administrators.

Adobe Connect refers to settings in the log4j file; it uses the settings in log4j, so much of the functionality is documented here: https://logging.apache.org/log4j/2.x/manual/appenders.html.

Looking specifically at the section entitled “Rollover Strategies” towards the middle of the page. It says this:

The default rollover strategy accepts both a date/time pattern and an integer from the filePattern attribute specified on the RollingFileAppender itself. If the date/time pattern is present it will be replaced with the current date and time values. If the pattern contains an integer it will be incremented on each rollover.

FilePattern itself, on that page, says this:

The pattern of the file name of the archived log file. The format of the pattern is dependent on the RolloverPolicy that is used. The DefaultRolloverPolicy will accept both a date/time pattern compatible with SimpleDateFormat and/or a %i which represents an integer counter. The pattern also supports interpolation at runtime so any of the Lookups (such as the DateLookup) can be included in the pattern.

The default configuration in Adobe Connect creates two files per day, AM/PM – see the following FilePattern:

filePattern=”${LOGS_DIR}/support/debug.log.%d{yyyy-MM-dd-a}”

Depending on what type of log retention is desired you may edit, the log4j Rollover Strategies. For example you may change the filePattern to drop the “-a” (to get one log file per day, timestamped) with or without an index counter.

 filePattern="${LOGS_DIR}/support/debug.log.%d{yyyy-MM-dd}-%i"

Whenever editing any of the Adobe Connect configurations files in xml, be sure to backup the file and also to restart the Adobe Connect services. Monitor performance on the server after any customization and be prepared to roll back changes in case there is an unexpected performance hit.

For more details on server-side logging in Adobe Connect see the following tech-note: https://blogs.connectusers.com/connectsupport/generating-server-side-logs-to-troubleshoot-on-premise-connect-installations/