Operations | Monitoring | ITSM | DevOps | Cloud

September 2019

Fixing Native Apps with Sentry

Whether it’s a computer game, IoT device, or high-performance backend, chances are you’re using a native language to develop this application. Hands down, by far the most popular choices today for native application development are C and C++. Okay, maybe not the most popular, but definitely the most prevalent. Some might even say “inevitable.”

Rethinking Application Performance Monitoring (APM): Sentry Raises $40 Million Series C

When I started Sentry in 2008 as an open-source side-project, I was solving a problem for myself. I wanted visibility and alerting around what errors occurred and when. I wanted to take errors out of log files and into an easily digestible dashboard.

Sentry Extends Best-in-Class Error Monitoring for Native Applications

Application crashes have a significant impact on customer experience, which can adversely affect a company’s reputation and revenue. Error and crash reporting is a unique feedback mechanism that provides true data about the quality of their product. Developer teams that create games, mobile applications, IoT, and other high-performance applications need rich insights into application health to quickly and continuously fix software errors with minimal impact.

Sentry for Native Crashes: Gaming, IoT, and Beyond

Application crashes have a significant impact on customer experience, which can adversely affect a company’s reputation and revenue. Error and crash reporting is a unique feedback mechanism that provides true data about the quality of their product. Developer teams that create games, mobile applications, IoT, and other high-performance applications need rich insights into application health to quickly and continuously fix software errors with minimal impact.

Distributed Tracing with Sentry: How to Find the Root Cause of Errors Across Applications

Implementing Sentry on all your services allows you to use distributed tracing to find the root cause of errors. Just because an error happens in a browser or mobile app, doesn’t mean the issue is with the frontend or mobile code. The issue could stem from an error with code in a different project that they interact with in some way. Distributed tracing empowers developers to find the actual cause of hard to fix issues.

Sentry and Rookout Integration: A Better way to Find and Debug Errors in Your Code

Rookout’s new Sentry integration empowers you to fix bugs faster than ever before. Sentry features allow you to identify the exact location of an error in your code. With the Rookout integration, you will find an additional prompt to debug the issue live, in production, in Rookout. With the click of a button you will see the same line of code from Sentry highlighted in Rookout’s IDE-like interface, without restarting, redeploying or adding more code. In Rookout you can set non breaking breakpoints and trigger the error again to receive the real time debug data.

Application Monitoring Overview: How to Track Errors with Sentry

A quick walkthrough of the Sentry application monitoring platform. In just a few steps, Sentry allows developers to identify and fix production errors across every application in the stack. Get started by installing the appropriate SDK for your platform or platforms. All unhandled exceptions will be automatically captured by Sentry, with individual errors rolling up into larger issues. You will be able to quickly learn the impact of specific problems, examine the stack trace, and get added context about the application state, so you can connect issues to the root cause.

How to secure ASP.NET Core apps with Azure Key Vault and Sentry

Joao Grassi — a .NET developer, front-end hobbyist, and friend of Sentry — likes .NET very much. So do we. With the help of one of Sentry’s top 10 SDKs, .NET developer teams process roughly half a billion .NET events every month. In this post, we strive for app security with Azure Key Vault and Sentry. By now, it’s not big news that ASP.NET Core is the future of web development with .NET.

How to Get Stronger Consistency Out of a Datastore

Welcome to our series of blog posts about things Sentry does that perhaps we shouldn’t do. Don’t get us wrong — we don’t regret our decisions. We’re sharing our notes in case you also choose the path less traveled. In this post, we stretch technologies to their limits to see real-time data while handling traffic spikes.

Sentry for Data: Easier, Faster Apache Beam Debugging

In our Sentry for Data series, we explain precisely why Sentry is the perfect tool for your data team. The present post focuses on how we used Sentry to make debugging Apache Beam easier (and faster). Since its creation, Sentry has embraced a single vision: help all developer teams build the best software, faster. We want to give developers the information they need to resolve issues quickly, without having to dig through noisy log lines.