How to disable agent logs AutoProbe.log and IntroscopeAgent.log

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• CA Application Performance Management (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

In a situation where there is limited disk space, how can the Introscope agent logs be stopped or limited by size?

Environment

Release : 10.7

Component : APM Agents, primarily Java Agent.

Resolution

To prevent the IntroscopeAgent from writing its log, comment out the following properties in the IntroscopeAgent.profile

     #log4j.logger.IntroscopeAgent=INFO, logfile

     #log4j.appender.logfile.File=../../logs/IntroscopeAgent.log

To stop the AutoProbe log from being created, comment out the following property, again in IntroscopeAgent.profile

     #introscope.autoprobe.logfile=../../logs/AutoProbe.log

Alternatively the path to the logfile can be left blank.

     introscope.autoprobe.logfile=

There are methods to restrict the logfile size without stopping it completely.

The Introscope Agent does have control for log file size and amount of files in these properties in the agent profile:

     log4j.appender.logfile.MaxBackupIndex=4

     log4j.appender.logfile.MaxFileSize=2MB

This effectively would use 10MB of disk space, for the active log (2MB) and four backup logs (4 x 2MB)

These values can be lowered to further reduce disk space but still have some logging enabled.

Note that if multiple agent processes use the same agent folder, there would be logs for each unique agent name.

For AutoProbe log, there is no configured property but a JVM argument can be added to limit the size of the AutoProbe log also:

     -Dcom.wily.autoprobe.logSizeInKB=1024

There is no rolling mechanism for this, this limit may be slightly exceeded depending on how much log information is still buffered waiting to be written to the log file.