Backtrace

Category: Engineering

Crash Deduplication: Triaging Effectively

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. 

Read More

Now Featuring: Console Release Notes

For our perceptive clients, you might have noticed that historically we’ve written robust release notes for our server components, but we haven’t included release notes for our web UI which we call Console. Now that more of our users are adopting Console as the primary means to manage, understand, and resolve crashes with Backtrace, we’ve decided to diligently update our community with Console release notes.

Check them out to find the latest updates to our web UI.

Read More

Error Report Analysis from the Command Line

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.

Read More