AppDynamics enables you to monitor performance and JVM health in a live production environment without affecting the end-user experience. Allowing you to visualize and map JVM dependencies, discover and map the tiers that interact with your JVM and Java Application JVM, AppDynamics gives you a deep view into your application performance
Monitor Business Transactions
With AppDynamics you can auto-detect business transactions from typical entry points into your JVM and understand how business transactions are carried out through various Java components like JMS, SOAP, EJB, and JDBC, that allows you to track JVMs from a high level.
Real-Time Alerting for the JVM
Get dynamic SLA base-lining and pro-active alerting to resolve performance issues whenever they arise, and warn production and application support teams much before end-user experience and service levels fall, with AppDynamics.
OutOfMemoryExceptions and Memory Leaks
AppDynamics offers a comprehensive view of heap usage, as well as utilization of key memory pools. You can automatically monitor memory leaks with minimal user analysis and quickly find the root cause with AppDynamics.
Detect Thrown Exceptions
AppDynamics reports and collects application run-time exceptions inside the JVM server, providing users with visibility of stack traces whenever user requests fail or timeout.
More on AppDynamics JVM Monitoring
Effectively monitor performance and understand the health of your JVM with the main Java profiling metrics such as throughput, exception rate, response time, and garbage collection time along with key system resources.
"AppDynamics replaced 5 tools we once used to try to troubleshoot application problems. Today, everyone goes to AppDynamics to quickly determine the root cause of the issue."
Customer Success at AppDynamics is More Than Just Software
"If you’ve been following our blogs regularly, you might have noticed we enjoy highlighting quantifiable benefits our customers have gained from using AppDynamics to manage their critical business applications in production. We take pride in their successes – and their success helps not only their organization but also their personal careers as well. So in today’s blog, I’d like to highlight some of the top-notch work our Customer Success team does...."
Death by Garbage Collection
"Every man and his dog knows that Garbage Collection (GC) is a “stop the world” event. Java memory becomes filled with redundant objects/data which over time must be collected so that memory can be reclaimed and reused by the JVM. When the GC thread in the JVM kicks in all other threads grind to a halt, giving the end-user an impression that the application is slow. It’s not such a big deal when GC runs for a few seconds, say, every minute, as this is typical for an active application that persists data frequently from databases (disk) to JVM (memory). The problem is when GC takes more than a few seconds, especially now that JVM memory and heaps can be as large as 16GB – collecting MBs can take seconds, but GBs can take minutes. I was troubleshooting a performance issue with a customer’s application last week and witnessed significant GC times of around 90 seconds. Here is what I found while troubleshooting...."