Stopping the Autoprobe log from expanding or getting excessively large.

Products

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

Issue/Introduction

Description:

A JVM's use of dynamically created classes, typically with a $ in the class name, can cause the Autoprobe log to grow excessively large. The logs are filled up with repeating class names :

Processing class com/package/class$name1
Processing class com/package/class$name2
Processing class com/package/class$name3
Processing class com/package/class$name4
Processing class com/package/class$name5
Processing class com/package/class$name1
Processing class com/package/class$name2
Processing class com/package/class$name3
Processing class com/package/class$name4
Processing class com/package/class$name5

The above is a simplified example. However, typically part of the class or package name could be made up of random characters.

Solution:

As no instrumentation is added to these classes, the problem is resolved usually by these steps:

• Insert a SkipPackage directive in the pbd file for the affected classes and add the
  
  Agent profile property introscope.autoprobe.logskippedclasses.enabled.
  
  For example, create a custom.pbd and add the line: SkipPackage com.package
  
  
• Include the custom.pbd in agent profile property:
  
  introscope.autoprobe.directivesFile=default-typical.pbl,custom.pbd,hotdeploy
  
  
• Add the following property to the agent profile :
  
  introscope.autoprobe.logskippedclasses.enabled=true
  
  
• Restart the agent and these classes should be no longer logged to the Autoprobe log.

Environment

Release:
Component: APMAGT