Blog
ArchiveTwitterFeed

Logs

Not everything that breaks is an error: a Logs and Next.js story

Logs
Stack traces are great, but they only tell you what broke. They rarely tell you why. When an exception fires, you get a snapshot of the moment things went sidew...
Read on

Trace-connected structured logging with LogTape and Sentry

Logs
As our applications grow from simple side projects into complex distributed systems with many users, the “old way” of console.log debugging isn’t going to hold ...
Read on

Using Sentry Logs to Debug a Dynamic Sampling Issue

Logs
Some of the team at Sentry spent this past quarter fixing bugs, more than 800 to be exact. Among them was a complex issue causing transaction spikes in our own ...
Read on

How we used Sentry’s User Feedback widget to shape Logs throughout beta

Logs
At Sentry, we build in public and we move fast. But moving fast means we don’t always get everything right on the first try. That’s where feedback comes in: it ...
Read on

Logs are Generally Available (Still logs, just finally useful)

Logs
When we started building Logs in Sentry we had one goal: make them useful for real debugging, not just another high-volume text storage. This meant making them ...
Read on

Logs in Sentry: Now in Open Beta

Logs
You’re looking at an error in Sentry—a failed payment in your Flask backend or an unexpected null in your Node API. You’ve got the stack trace. The request deta...
Read on

A Guide to Logging in React Native

Logs
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 informa...
Read on
© 2026 • Sentry is a registered Trademark of Functional Software, Inc.