Application crashes are a serious concern that should be on every Electron developer’s radar. No matter your level of expertise, you’ll want to know when crashes impact your users and make sure you have the necessary data to (have someone) fix the issue. Luckily, Electron has built-in facilities to generate and submit crash reports across supported platforms through Breakpad, Crashpad, and Electron’s crashReporter API.
But what options do you have available for a crash reporting server? Look no further: in this post, we’ll show you how to get up and running quickly with Backtrace & Electron and demonstrate our unique feature set that makes Backtrace the best crash reporting option for Electron.
Depending on your application, crash reports may come in at the rate of a few to many thousands a day. Regardless of scale, fatal errors slip through the cracks, and even for the ones you do catch, it’s difficult to understand crash impact and to differentiate unique crashes from crash groups. Your ability to quickly triage and prioritize these fatal errors is crucial to your ability to act on them with urgency. Triage and prioritization relies on determining impact, like which users are affected by a crash or which crash has the highest impact on revenue. Backtrace helps you do this effectively through our deduplication systems.
Backtrace now includes a completely new storage and indexing subsystem that enables engineers to slice and dice hundreds of attributes in real-time easily so they can better triage and investigate errors across their ecosystem, all from the comfort of their command-line environment. When an application crash occurs, there are hundreds of data points that may be relevant to the fault. This can range from application-specific attributes, such as version or request type to crucial fault data such as crashing address, fault type, garbage collector statistics to environment data such as system memory utilization.
Read on to learn more how you can interact with Backtrace from the command line for crash report and error investigation.
Earlier this year we published a post titled Implementing A Debugger: The Fundamentals. This post gave an overview of debuggers, what they do, and how they work. In today’s post, we build upon this knowledge and talk about our journey of extending Backtrace’s debugger to support Go. Intro If you have the time and haven’t… Read More
Think about the workflow the last time you pushed a release. Release cut, QA tests passed, and the monitoring games begin. Latency numbers, RPS, and CPU look normal, nothing to be alarmed of…An hour later, things start to break. Customers are calling in complaining about disconnects and the machines that are still up are overloaded. In… Read More