Operations | Monitoring | ITSM | DevOps | Cloud

Crash Reporting

A Look Back at 2023

As we've turned the final pages of 2023 and now set our sights on 2024, it felt like an appropriate moment to pause, reflect, and shine a light on the steps we've made over the past year at BugSplat. There are a couple of compelling reasons to do this: First, we recognize that some of our key updates might slip under the radar amidst the hustle and bustle of daily tasks. Highlighting these changes is our way of giving you a second chance to discover some useful new features at your disposal.

Sponsored Post

Symbolicating stack traces from Apple system libraries

In the world of software development, quickly finding and fixing errors drives better experiences for both end-users and developers. One key tool in this process is the symbol map, which records debugging information that was lost in the compilation process. Symbol maps (or source maps if we're talking JavaScript) connect the code developers write to the minified code in production, making it easier to decipher crashes by pinpointing the exact source code that caused the error.

Auto-Creating Defects from BugSplat in Your Defect Tracker

At BugSplat, we're always looking for ways to seamlessly integrate critical crash data into the support workflow. Another step in that quest has just been launched - the ability to automatically create defects from BugSplat databases in attached third-party trackers like Jira, Github Issues, Azure DevOps and more. This isn't just a new feature - it's a game-changer. Here's why.

Sponsored Post

Best practices for tracing and debugging microservices

Tracing and debugging microservices is one of the biggest challenges this popular software development architecture comes with - probably the most difficult one. Due to the distributed architecture, it's not as straightforward as debugging traditional monolithic applications. Instead of using direct debugging methods, you'll need to rely on logging and monitoring tools, coding practices, specific databases, and other indirect solutions to successfully debug microservices.

How to launch games that don't crash (often)

Building and supporting a video game project is challenging. It is a complex and intricate process that balances difficult time constraints and ambitious goals while keeping a highly engaged and demanding user base happy. Game developers need every advantage possible in the development and support process to succeed. One of the best ways to ensure that a game is successful is to make sure that every shipped version of the game project contains as few crash-causing defects as possible.

5 Signs You Have Outgrown Your Mobile Monitoring Solution

Imagine you start a new hobby — let’s say bike riding. You don’t want to invest a lot in a bike because you’re not sure that you’ll like it. Luckily, you snag a free bike from a friend — it’s clunky, but the price is right. You start out with short rides around your neighborhood and eventually find yourself riding every day, going on longer and longer rides. Your free, heavy bike is holding you back.

Introducing the New Batch Reprocess Tool

At BugSplat, we're constantly searching for ways to help our users save time and energy while fixing crashes. We do this by providing them with more tools to quickly identify the underlying defects that cause problems in their apps. In that vein, we're excited to introduce the Batch Reprocess Tool (view technical doc here), a new feature that allows users to quickly select a set of crashes and have them reprocessed in bulk.