Monitoring != Root cause analysis

APM gives news, yCrash gives answer

APM tools like AppDynamics, New Relic, Dynatrace are excellent monitoring tools. They monitor your application and report that CPU spiked by x%, memory degraded by y%, response time shot up by z seconds. But they don’t answer why CPU spike up? Why memory degraded? Why response time shot up? To troubleshoot the problem, your operations engineer has to capture GC log, thread dump, heap dump, netstat, vmstat….. several few more artifacts and analyze these artifacts to identify what is causing the degradation in performance/availability characteristics. yCrash automates the artifact capturing and analysis part. yCrash reports the exact line of code that is causing the problem.

Overhead

APM agents run within your application’s JVM. yCrash agent runs only when it’s triggered. At other times, it’s dormant. Even when it runs, it runs on the host and not within the JVM.

Even though APM agents claim to add less than 3% overhead, it’s far from reality. But for heap dump, all other data captured by Ycrash doesn’t add any measurable overhead. However, heap dump is an intrusive operation and pauses your application. Thus, heap dump should be obtained when it’s necessary.

Macrometrics, Micrometrics

APM reports macrometrics like CPU utilization, Memory utilization, response time, component level response time.

yCrash reports and analyzes micrometrics like GC throughput, Object creation rate, object promotion rate, GC latency, thread states, thread group size, list of open file descriptors, … For more details on this topic, you can refer to this article.

Taste of pudding is in eating

Recently a major telecom company had an outage due to memory leak in it’s application. Their APM solution generated alerts stating the memory was spiking up. Telecom company used yCrash to diagnose the problem. yCrash reported the exact objects that were causing the memory to leak. Apparently, it turned out that the leak was caused by AppDynamics agent itself that was running within the application. Below screenshot shows ycrash reporting the AppDynamics agent that is causing the memory leak.

Fig: Screenshot showing yCrash reporting the AppDynamics agent causing the memory task.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

A WordPress.com Website.

Up ↑

%d bloggers like this: