Investigating Performance Problems in AppDynamics

Welcome to this tutorial on investigating performance problems in AppDynamics. AppDynamics is a powerful application performance monitoring tool that allows you to monitor and analyze the performance of your applications and infrastructure. In this tutorial, we will explore the steps to investigate performance problems using AppDynamics, provide examples of commands or code, discuss common mistakes to avoid, answer frequently asked questions, and summarize the best practices.

Example Commands or Code

Here are a few examples of commands or code that can be used to investigate performance problems in AppDynamics:


The above command sets the log level to DEBUG, enabling more detailed logging information for troubleshooting performance issues.

Steps to Investigate Performance Problems in AppDynamics

Follow these steps to investigate performance problems using AppDynamics:

  1. Identify the Problem: Gather information about the performance problem, including symptoms, affected components, and any error messages or warnings.
  2. Collect Metrics: Use AppDynamics to collect relevant performance metrics, such as response time, throughput, and error rates.
  3. Analyze Key Performance Indicators (KPIs): Review the KPIs to identify any anomalies or deviations from the expected behavior.
  4. Drill Down to Transactions: Identify the transactions or requests that are experiencing performance issues.
  5. Review Transaction Snapshots: Analyze transaction snapshots to understand the end-to-end flow, identify bottlenecks, and pinpoint any slow or problematic components.
  6. Check Error and Exception Logs: Examine error and exception logs to identify any recurring errors or exceptions that may be impacting performance.
  7. Investigate Infrastructure Metrics: Evaluate the infrastructure metrics, such as CPU usage, memory usage, and disk I/O, to determine if any resource constraints are contributing to the performance problems.
  8. Use Diagnostic Tools: Leverage AppDynamics' diagnostic tools, such as call graphs and code-level visibility, to analyze the application code and identify performance bottlenecks.
  9. Collaborate and Share Findings: Collaborate with relevant teams, such as developers and operations, to share your findings and gather additional insights.
  10. Implement Fixes and Monitor: Based on the investigation, implement necessary fixes or optimizations and monitor the application's performance to ensure the problem is resolved.

Common Mistakes to Avoid

  • Not collecting enough data and metrics to accurately diagnose the performance problem.
  • Overlooking the importance of analyzing both application and infrastructure metrics.
  • Not drilling down to the transaction level to understand the full flow and identify potential bottlenecks.
  • Failure to leverage diagnostic tools and code-level visibility for detailed analysis.
  • Not involving the relevant teams and stakeholders in the investigation process.

Frequently Asked Questions (FAQs)

  1. How can I identify the root cause of a performance problem in AppDynamics?

    Start by analyzing transaction snapshots and reviewing infrastructure metrics. Look for any abnormalities or bottlenecks that may be causing the performance problem. If needed, drill down further into the code-level visibility to identify specific areas of improvement.

  2. What should I do if AppDynamics does not capture certain performance metrics?

    Check the instrumented code to ensure that the desired metrics are being captured. Verify that the application and tier configurations in AppDynamics are correctly set up to collect the required metrics.

  3. How can I troubleshoot a slow database query using AppDynamics?

    Review the database metrics and identify the slow query. Analyze the query execution plan and consider optimizing the query, adding indexes, or caching frequently accessed data to improve performance.

  4. What are some common causes of high response time in AppDynamics?

    High response time can be caused by various factors, such as network latency, resource contention, inefficient code, database issues, or infrastructure limitations. Investigate each potential cause to identify the root problem.

  5. When should I engage AppDynamics support?

    If you have exhausted your troubleshooting efforts and are unable to identify the root cause of the performance problem, it is advisable to engage AppDynamics support. They can provide expert guidance and assistance in resolving complex issues.


Investigating performance problems in AppDynamics requires a systematic approach to identify and resolve issues. By following the steps outlined in this tutorial, analyzing key performance indicators, drilling down to transactions, and utilizing diagnostic tools, you can effectively investigate and troubleshoot performance problems. Avoiding common mistakes, involving relevant teams, and implementing fixes will help improve application performance and user experience.