Operations | Monitoring | ITSM | DevOps | Cloud

Breakpoints and console.log statements might save your sanity during local dev, but production issues are another story. In prod, your errors might be distributed across different microservices, or hidden in minified code. Good luck hunting those down. That’s where Sentry’s traces and spans come in, offering you easy visibility into every network request, API call, DB fetch and more in a full-stack, distributed environment.

Have you ever encountered a confusing error message that left you wondering what went wrong in your Python code? You’re not alone. Even the most experienced developers run into exceptions, making it essential to understand how to handle them effectively. While basic syntax errors can be caught early by code editors and debugging tools, more complex issues often arise at runtime, requiring a structured approach to exception handling.

This represents a big step to getting JavaScript debug ids more formally recognized across the JavaScript ecosystem. It also shows how Sentry is developing the maturity to lead open standards and engage in consensus building. Want to learn more? Read on!

You're reviewing your production metrics when suddenly an error spike appears on your dashboard. Your immediate thought isn't "how do I build a new view to investigate this?" but rather "how do I find out the cause quickly?" This is exactly what happened to one of our engineering teams last month when they spotted an unusual pattern in their API response times. Instead of running ad-hoc queries from scratch, they turned to a custom dashboard they had built after a past incident.

A few weeks ago, we introduced anomaly alerts to early adopters. Today, we’re excited to announce that anomaly alerts are officially in open beta and available to all Sentry users on the Trial, Business, or Enterprise plans.

Basic console logging is a good starting point for debugging and understanding an app. For larger, more complex apps, it’s helpful to include additional information and persist logs. In this guide, you’ll learn how to create and view logs in React Native and how to create and save custom logs to a file. We’ll focus on JavaScript logs.

Whether it's a boss fight freeze or a sudden disconnect in multiplayer, crashes break immersion and make your players mad. Debugging these issues across multiple platforms—each with its own error-reporting system—only makes things harder.

A few years ago, it was all about Blockchain; before that, IoT, then Big Data, and even earlier, the Cloud. Each era brought a paradigm shift of sorts, drawing huge investments and promises. Some delivered, some didn’t, but they each brought advancement in tech. Today, we find ourselves fully embracing the AI hype cycle that started circa 2022 with OpenAI.

Mobile devs know the struggle. Small regressions can cause big issues in production, and fixing them isn't as easy as pushing a quick patch. Unlike a web app, shipping fixes for apps means navigating app store approvals, and often hopping on meetings with customers to debug because mobile issues can be so challenging to recreate. Catching these issues before the 1-star reviews roll in is crucial. Luckily, Sentry just made it easier than ever.

Which JS framework is the most performant? React, Vue, Svelte, Angular,…? When trying to answer this question, we often get lost in comparing benchmarks for reactivity, bundle size, memory usage and other factors. Of course we want to choose the best framework to create performant apps! But your app will only benefit from framework performance if you also follow best practices for performance optimization of web apps in general, and React apps in particular. So, where to start?