Backtrace Customers Handle Errors Before Users Churn
Game Studios, CDNs, IoT, Advertising, Media, Messaging, SaaS, and more
TRUSTED BY COMPANIES LIKE
DON’T TAKE OUR WORD FOR IT…
Lumberyard is a AAA game engine with millions of lines of C++ code…. Before Backtrace, our QA team spent a lot of time deduping crashes, then classifying them as to which team they should go to–graphics crash, low level crash, etc.–before we could fix the issue.
Backtrace cut our MTTD by more than 90% by automating our crash aggregation. Now our developers can focus on building new features rather than chasing down bugs.
It is nice to see crash dump automation like Backtrace come to market in a way that helps reduce a lot of headaches, and also helps automates processes for smaller teams who do not have the luxury of a full QA Staff on board to manage, track, and report crashes on a daily basis.
Where every other debugging tool has failed for our large workloads at Fastly, Backtrace succeeds, quickly providing data that gives us a huge head start.
With Backtrace’s fast and accurate crash analysis, we can quickly identify, analyze, and address critical issues prior to a global release, ensuring our customers continue to have a high-quality experience.
Backtrace was able to reduce a highly inconsistent hours-to- days process to minutes. A two minute MTTD and a 23 minute MTTR for a tested fix involving a core library. The future looks way more comfortable than the past.