Developers and operations personnel complain the Controller tracks many irrelevant Java classes and methods. How does a Performance Analyst exclude this unhelpful information?

Question

Options

• AConfiguration > Baselines and create a new dynamic baseline
• BEdit the mbeans-server.xml file to delete the irrelevant methods
• CConfiguration > Instrumentation > Call Graph Settings and exclude irrelevant packages
• DEdit the controller-info.xml file to exclude irrelevant methods

• A
  4% (1)
• B
  8% (2)
• C
  71% (17)
• D
  17% (4)

Explanation

To streamline the monitoring process and enhance the relevance of collected data, AppDynamics allows Performance Analysts to exclude certain Java classes and methods from instrumentation. This is done through the "Configuration > Instrumentation > Call Graph Settings" menu, where irrelevant packages and classes can be specified for exclusion. This approach prevents the AppDynamics agent from tracking unnecessary or irrelevant methods, thus reducing overhead and focusing on the most critical aspects of application performance.

No community discussion yet for this question.