Crash Reporting


The Great Irony of Serverless Computing

Working with Serverless computing is like riding an electric bike. You get speed, flexibility, automatic assistance to scale with ease. Development is usually hassle-free because you can focus on code and only pay for usage of the service. Except when your users hit an error. Debugging that issue feels like your bike’s battery just died while climbing a steep hill.


How we scale Raygun's architecture to handle more data

Due to the huge importance of sourcemaps in the workflow of our customers, sourcemaps are a crucial part of our Crash Reporting offering. We constantly strive to stay ahead of our customer demands as the amount of data we process continues to grow. We identified the sourcemapping process as an area ripe for performance improvement, so we took it apart and looked at exciting ways to build it from the ground-up using cutting-edge tech.


Support for Crashpad Attachments

BugSplat now supports attachments for Crashpad out of the box. Developers can include additional files with the Crashpad crash upload using the newest release of the BugSplat Crashpad SDK. This release includes updated examples that show how to include Crashpad attachments for Windows, Linux, Android, Qt Windows, and Qt Linux (but not yet for macOS). Before this change, including attachments with Crashpad out of the box was difficult.


Introducing Android Crash Reporting with BugSplat

BugSplat users can now collect Android crashes with the Crashpad SDK. If you're supporting a cross-platform C++ application, porting a C++ application to Android, or creating a new NDK library from scratch, you can now use BugSplat to track, collect, and debug your Android crashes. This will bring the same in-depth view of crash events you get with BugSplat on other languages to your Android application.


Never miss another crash! Instana's Crash Detector brings real-time Abnormal Process Termination analysis to Linux

Irrespective of how many levels of abstraction are constantly being introduced like containers and serverless, your code is run by the operating system in processes. And those processes can and will encounter issues, causing them to exit with erroneous status codes. In other cases, the operating system or something else running on it, will kill your processes, or send them other signals that will cause them to shut down.


Make sense of application issues with Datadog Error Tracking

When your applications raise errors, you need a way to make sense of them so you can set priorities, start troubleshooting, and gauge the success of your efforts. Errors can appear within the thousands of browser sessions and backend hosts running your software, making it difficult to find meaning within the noise. This is especially true of frontend errors, where seemingly endless permutations of browser version, location, and other environmental details can make it hard to spot trends.


Introducing our new Java Spring Error Monitoring SDK

We’re excited to announce that we’ve strengthened our solution for Java Spring. Spring developers can now integrate Rollbar into their Java Spring Boot and Spring Web MVC applications even more quickly and easily. With our new SDK, instrumentation and getting real-time actionable error alerts takes just a few minutes. Spring has consistently been one of the most popular Java frameworks and we want to make sure we’re consistently offering the best possible solution for it.


Crash by API

Crashes are something we know a thing or two about. We see a lot of reasons why apps crash, but we also see when a lot of popular mobile apps crash at once, that’s something we notice. Crashes across many mobile apps at the same time is not typically a result of an app-specific code update. I mean, there’s a non zero chance that hundreds of developers published broken apps… but these widespread issues are likely a result of two things.