At BugSplat, we’re constantly striving to enhance our platform to meet the evolving needs of our users. We’re excited to introduce our latest feature: Custom Attributes. This powerful addition allows developers to attach any number of custom attributes to crash reports, making BugSplat more customizable to your individual use case and enabling deeper integration with your projects.

Between your app server and your customer's fingertips, your mobile application or website's performance depends on many factors. Often, what you give may not be what the customer gets, as several things can get in the way, such as bottlenecks, server performance issues, network woes, and un-optimized code. All these factors prevent your customers from experiencing fluid, fast, and functional apps and websites as intended.

NET Aspire is a new type of project and set of NuGet packages that make it easier to coordinate the multiple moving parts of a cloud-native web application. Announced near the end of 2023, .NET Aspire is currently in Preview 6, so still a work in progress. We’ve just released Raygun4Aspire, our Crash Reporting client for Aspire applications.

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.

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.

The Raygun ingestion pipeline is kept pretty busy processing over 90 million crash reports every day. So needless to say, we need the processing pipeline to be as efficient as possible to reduce resource usage and avoid costly scaling.

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.

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.