How does a Performance Analyst exclude this unhelpful information?

Developers and operations personnel complain the Controller tracks many irrelevant Java classes and

methods.

How does a Performance Analyst exclude this unhelpful information?
A . Configuration > Baselines and create a new dynamic baseline
B . Edit the mbeans-server.xml file to delete the irrelevant methods
C . Configuration > Instrumentation > Call Graph Settings and exclude irrelevant packages
D . Edit the controller-info.xml file to exclude irrelevant methods

View Answer

Answer: C

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.

Reference: AppDynamics documentation on Call Graph Settings: This section details how to configure call graph settings, including the exclusion of specific classes and methods from instrumentation, to optimize performance monitoring.