Are you familiar with the four golden signals of Site Reliability Engineering (SRE): latency, traffic, errors, and saturation? Whether you’re a developer or an operator, you’ve likely been responsible for collecting, storing, or analyzing the data associated with these concepts. Much of this data is captured in application and infrastructure logs, which provide a rich history of what is happening behind the scenes in your workloads.

In cases, when a crash happens in your Android application, you want more context on what occured before the issue — kind of like following breadcrumbs to the exception. Our SDKs automatically report breadcrumbs for activity lifecycle events, system events, HTTP requests, and many more. Now, Android developers will also see UI events listed as breadcrumbs and get the full picture of what happened without ever having to recreate the issue.

The mere mention of a serious software error can strike fear into the heart of any developer, project manager or tech leader. The wrong error in the wrong system can be incredibly expensive and difficult to resolve, not to mention humiliatingly public. Catastrophic software errors are mercifully rare these days, but the potential for chaos, PR disasters and spiraling costs still remains.

Selecting the best sentry alternatives for error monitoring is likely to be difficult. It might be difficult to sort between the features, benefits, and drawbacks of many software companies and sellers. Let's talk about how to make this process easier by looking at the eight best alternatives to Sentry. Sentry is open-source application performance and error-tracking tool that allows developers to track and fix errors in real-time.

You are likely to face challenges in selecting the best alternatives to Sentry for error monitoring. It can be daunting to read through multiple software companies and vendors to note their features, benefits, and shortcomings. Let’s discuss simplifying this process by covering the six best alternatives to Sentry error monitoring. Feel free to navigate this guide using the links below.

Debugging errors is an essential component to SRE and developer workflows. “How do we prioritize and isolate JavaScript errors more effectively?” is a top challenge we hear from engineering teams looking to improve end-user experience. Therefore, we are excited to announce the general availability of Splunk RUM frontend error monitoring.

Bugsnag is a stability error monitoring solution which captures unhandled exceptions, diagnostic data, and version information in browser, mobile and server-side applications via open source SDKs for 50+ software platforms. By default, Bugsnag libraries capture all crashes (handled exceptions are optional), version numbers, and session information to help engineering teams proactively surface issues and save time fixing bugs.

Say you've been tasked with monitoring an application, so you set up some alerts to let you know when errors are coming in. The minutes roll by, the errors start coming... ...and they don't stop coming... Oh my, there seems to be quite a few errors coming through. Alerting on each error isn't going to help, better report on changes in the error rate instead right? Not quite.

FastAPI is a high-performance web framework for building APIs with Python that has been growing in popularity. In this article, Stefano Frassetto shows us how to set up error monitoring for a FastAPI app using Honeybadger.