IBM APM Application Performance Management 8.1 server logs - rotation log settings

So I searched around and here is what I have found so far for the main components included in APM server:

- APM MIN :

In /opt/ibm/wlp/usr/servers/min/server.xml file, use:

 <logging"100" maxFileSize="10" consoleLogLevel="OFF”  traceSpecification="*=INFO"/>

- MongoDB :

possibly use some settings in the “# Logging” paragraph of /opt/ibm/mongodb/etc/mongod.conf file.

- Kafka Message Broker :

check /opt/ibm/kafka/config/log4j.properties file, and follow some guidelines like documented here :

https://community.hortonworks.com/content/supportkb/49706/kafka-log-file-rotation-based-on-file-size.html

- MIN Derby database:

check /opt/ibm/gaian/gaiandb_config.properties file

Change this setting if needed:

# Beyond this max size, GaianDB will alternate between logging to gaiandb#0.log and gaiandb#1.log, switching every time the max is reached

# The initial gaiandb.log will not be lost.

LOGFILE_MAX_SIZE_MB=100

- Server1 :

In /opt/ibm/wlp/usr/servers/server1/server.xml file, use:

<logging maxFiles="100" maxFileSize="10" consoleLogLevel="OFF"

- APMUI :

In /opt/ibm/wlp/usr/servers/apmui/server.xml file, use:

<logging consoleLogLevel="OFF" traceSpecification="*=info" maxFiles="100" maxFileSize="10"/>

That being said, also as documented here:

https://www.ibm.com/support/knowledgecenter/en/SSHLNR_8.1.4/com.ibm.pm.doc/install/trouble_logs_server.htm

"Cloud APM server log files start wrapping when the configured number and size of the log files is reached. The Cloud APM server disk space requirements account for the number and size of the log files that are configured by default. It is recommended that you use an OS agent to monitor disk space usage on the Cloud APM server."

So the default settings for APM server log file size and number of files should be left untouched, except if you are not able to capture some meaningful oir relevant errors in the logs, and they are wrapping too quickly while reproducing your issue.