In the series of chaos engineering articles, we have been learning to simulate various performance problems. In this post, let’s discuss how to simulate StackOverflow error. StackOverflow error is a runtime error. In this post let’s discuss how to simulate StackOverflowError, diagnose it and solve the problem.Continue reading “Chaos Engineering – Stackoverflow Error”
In the series of chaos engineering articles, we have been learning to simulate various performance problems. In this post, let’s discuss how to simulate thread leaks. ‘java.lang.OutOfMemoryError: unable to create new native thread’ will be thrown when more threads are created than the memory capacity of the device. When this error is thrown, it will disrupt the application’s availability.Continue reading “Chaos Engineering – Thread Leak”
Lets understand how GCeasy & yCrash differ from each other in the following table.Continue reading “What is the difference between GCeasy and yCrash?”
yCrash app is a non-intrusive, secure, instant root cause analysis tool. It captures thread dump, heap dump, GC log, netstat, vmstat, top, and several more artifacts, right when the problem is happening in the production. It instantly analyzes all the artifacts & generates a root cause analysis report in the dashboard. Watch this below video clip to get a detailed overview of yCrash!
yCrash provides a safe and secure mechanism to troubleshoot production problems. In this article, let’s discuss about the safety measures provided by yCrash.Continue reading “yCrash – safe and secure way to troubleshoot”
yCrash is our end-end root cause analysis solution built on top of our successful products GCeasy, fastThread, HeapHero. yCrash leverages the same underlying parsing engine and ML algorithms of these 3 tools. On top of it, yCrash provides additional capabilities. This document intends to highlight those key capabilities.Continue reading “GCeasy + fastThread + HeapHero + lot more … = yCrash”
Please refer yCrash documentation to follow the installation instructions.
APM gives news, yCrash gives answer
Industry has seen cutting-edge Application Performance Monitoring tools (i.e., AppDynamics, NewRelic, Dynatrace) and infrastructure monitoring (i.e., Nagios, Ngmon) tools. These monitoring tools are great at detecting the symptoms of the problems. i.e., they can detect CPU spiked by x%, memory degraded by y%, and response time shot up by z seconds. But they dont answer the question: Why did the CPU spike up? Why is memory degraded? Why is response time increased?
To answer these questions, you need to capture garbage collection logs, thread dumps, heap dumps, nestat, and several more artifacts from your application. As the next step, you need to analyze these cryptic tedious dump files to identify the root cause of the problem. yCrash – the root cause analysis tool does this for you automatically. yCrash captures and analyzes these artifacts and identifies the root cause of the problem instantly.Continue reading “Monitoring != Root cause analysis”
yCrash server can be configured to send notification emails whenever new incidents are reported. Based on the hostname, app name from where the incident is reported, you can configure to send alert emails. Here are some sample rules:Continue reading “Configure mail server”