Lets understand how GCeasy & yCrash differ from each other in the following table. GCeasyyCrashWhat is the purpose?GCeasy is used to optimize Garbage collection pause times & throughput.yCrash is an end-end root cause analysis solution. It answers the questions: Why did your application slow down? Why did the CPU spike up? Which objects in memory... Continue Reading →
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... Continue Reading →
yCrash provides a safe and secure mechanism to troubleshoot production problems. In this article, let's discuss about the safety measures provided by yCrash. Data archival Production dump files tend to contain sensitive information such as IP addresses, credit card numbers, SSN, VAT numbers ... and they also tend to be very large in size (several... Continue Reading →
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. Quick Overview In this video clip. our... Continue Reading →
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... Continue Reading →
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: If incident is reported on ‘host1.mycompany.com’ device then send email notification to user1@mycompany.com If incident is reported... Continue Reading →
