What are AppDynamics application troubleshooting tools, by issue?
AppDynamics provides various tools for troubleshooting different application issues. Our official documentation includes several pages dedicated to troubleshooting different application components.
In this article
Find recommended tools to apply in specific use cases, including:
In addition, check out these consolidated references:
Slow application
USE CASE
Imagine what you might do in a situation where your service desk calls, telling you that there are complaints about slow logging into your application. What do you do?
And by the way, have you checked Analytics to see how the issue impacted your business?
BACK TO CONTENTS
Sudden increase of exceptions
USE CASE
An alert reported a higher than usual error rate for certain Business Transactions, and we simultaneously spotted a sudden increase of exceptions in the application dashboard. How do we analyse it?
BACK TO CONTENTS
Networking bottleneck
USE CASE
While analyzing a Business Transaction, you discovered a lot of issues between Tiers and towards the shared backend.
None of the application information, or system, points to a specific root cause but you can see the response time is unexplainably high. Before escalating to the network team, how can you further troubleshoot the Network Visibility yourself?
BACK TO CONTENTS
Analyzing the JVM
USE CASE
You notice bottlenecks on all calls processed by a Tier (specifically a JVM cluster). While analyzing you discover that the Java Virtual Machines are under high load, but you can't pinpoint it to a specific piece of code causing the high resource load, and your team of developers needs more detail about the problems you discovered in AppDynamics.
This kind of bottleneck often occurs due to underlying hardware, the JVM I/O Resources, and the JVM memory management which you now start to analyze in more detail.
BACK TO CONTENTS
Digging into problematic asynchronous calls
USE CASE
What if the application you monitor takes advantage of multithreading solutions? These documents will help you discover potential problems in the AppD Controller. See the AppDynamics Documentation for:
BACK TO CONTENTS
Health Rule violation analysis
USE CASE
Let’s say you get a new email from the AppDynamics Controller, showing a Health Rule violation. You ask yourself essential questions like:
- When was the Health Rule violated?
- Is the violation still ongoing? or not?
- What condition(s) deviated from the normal performance, and for which entities?
BACK TO CONTENTS
Performance impacting business
USE CASE
Based on your research, you know that your organization’s profits are highly correlated to user experience, and consequently to the performance of crucial business transactions. So, you look for a dedicated tool for such a purpose.
BACK TO CONTENTS
Degraded cluster health
USE CASE
Your organization is facing the challenge of monitoring Kubernetes environments at scale. You would like to maintain visibility into the performance and health of the Kubernetes cluster, its underlying infrastructure, and running applications. You don’t want to put too much effort into deploying and maintaining the Agents.
What can AppDynamics offer in this scenario?
BACK TO CONTENTS
Mobile app crash
USE CASE
Your mobile application’s end users start complaining in their Google Play and App Store reviews, and the app’s ratings fall. From their comments, you conclude that the application continuously crashes. You need an immediate root cause analysis. Your application team wants to start in AppDynamics. Where to look?
This time, you were able to solve the issue once you had a look at it. But how could you prevent running into similar issues in the future, without needing to rely on customer feedback?
BACK TO CONTENTS
Performance pattern
USE CASE
Unquestionably, not every IT system is equally active 24/7, and the same is true for your application. At night, load decreases significantly. But Saturday afternoons, the application typically experiences a noticeable increase in active users.
Will AppDynamics adjust to changing characteristics of the application metrics?
What if a maintenance window or other planned abnormality is approaching, and you would like to suppress alerting for a set time?
Or (even better) how can we show that an abnormal behavior event (like Black Friday) is behaving normally despite the expected higher load? — e.g., "when does our system break, versus when the system is just under load or stress?"
BACK TO CONTENTS
UX design challenges
USE CASE
In a competitive environment, every detail matters. Your UX design team puts a lot of effort into distinguishing your application from the competition: with outstanding UX for both browser and web applications.
How can the design team understand your end users more fully? Do both front-ends perform well? Can AppDynamics be close enough to the end user to help in defining the persona?
Back to Contents
Identifying expensive dB queries
USE CASE
It's an old truth that the database is “always the bottleneck”. Some transaction snapshots were categorized as slow and very slow. You see no pattern in neither Business Transaction, nor nodes. Might some transactions share the same, expensive dB queries?
BACK TO CONTENTS
Index | Troubleshooting resources by scenario
BACK TO CONTENTS
Additional Resources
BACK TO CONTENTS
