The "Application Health Report" is a built-in scheduled report in AppDynamics that includes vital

metrics such as load, response time, and error graphs. This report provides a comprehensive

overview of the application's health and performance, making it an essential tool for Performance

Analysts to regularly review and share with stakeholders to ensure the application meets

performance standards and user expectations.

Reference:

AppDynamics documentation on Reporting: Covers the types of reports available within

AppDynamics, including the Application Health Report, detailing its contents and how to schedule

and customize it.

AppDynamics documentation on Application Performance Management: Provides an overview of

key performance indicators and metrics critical for assessing application health, many of which are

included in the Application Health Report.

When analyzing database performance in AppDynamics, the "Queries" tab within the database

collector view is where a Performance Analyst should navigate to find slow queries. This tab presents

a list of database queries executed by the application, highlighting those with long execution times,

which are potential bottlenecks impacting application performance.

Reference:

AppDynamics documentation on Database Monitoring: Details the database collector feature,

including how to use the Queries tab to identify and analyze slow database queries.

The Metric Explorer in AppDynamics allows Performance Analysts to define and visualize Key

Performance Indicators (KPIs) from a selection of metrics. By accessing the Transaction Analytics data

set, analysts can create custom dashboards that focus on the metrics they've determined to be

critical KPIs for their application's performance.

Reference:

AppDynamics documentation on Metric Explorer:

Development Level Monitoring in AppDynamics is designed for use in a lower volume, non-

production environment. For a default configuration, Development Level Monitoring will get

automatically disabled if the monitored environment exceeds a threshold, typically a maximum of

1000 calls per minute, and the Maximum heap utilization percentage goes above 95%. These

thresholds are in place to prevent excessive overhead in a production environment where such

detailed monitoring could impact performance.

Reference:

AppDynamics documentation on Agent Configuration: Provides information on configuration settings

for monitoring levels, including when Development Level Monitoring is automatically disabled due

to exceeding thresholds.

To plot Host CPU and GC (Garbage Collection) Time Spent in a single view, the "JMX tab under 'Tiers

and Nodes'" and the "Metrics Browser" are the appropriate methods. The JMX tab provides access to

Java Management Extensions (JMX) metrics, including those related to GC time. The Metrics Browser

allows for the customization and aggregation of various metrics, including Host CPU usage and GC

metrics, enabling a combined view of these critical performance indicators.

Reference:

AppDynamics documentation on Monitoring Tiers and Nodes: Discusses the JMX metrics available

for Java applications, including garbage collection details.

AppDynamics documentation on the Metrics Browser: Describes how to use the Metrics Browser to

view and analyze a wide range of performance metrics.