Vercel Logs on Sentry
Set up a Log Drain from Vercel and monitor all of your application data in Sentry. We'll take a quick look at how to set up a Log Drain, and show you two quick examples of how they can be used.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Paginating large datasets in production: Why OFFSET fails and cursors win
The things that separate an MVP from a production-ready app are polish, final touches, and the Pareto ‘last 20%’ of work. Many of the bugs, edge cases, and performance issues will come to the surface after you launch, when the user stampede puts a serious strain on your application. If you’re reading this, you’re probably sitting on the 80% mark, ready to tackle the rest.
Logging in React Native with Sentry
Logs are often the first place dev teams look when they investigate an issue. But logs are often added as an afterthought, and developers struggle with the balance of logging too much or too little. As a seasoned developer, you may remember a time when you were asked to investigate an issue and then handed a 200 MB plaintext log file. Three hours and four Python scripts later, you would realize that the problem was in a different component.
Not everything that breaks is an error: a Logs and Next.js story
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 sideways, but the context leading up to that moment? Gone. That's where logs come in. A well-placed log can be the difference between hours of head-scratching and a five-minute fix. Let me show you what I mean with a real bug I encountered recently.
How to debug a Next.js production bug with Logs and Sentry
Stack traces tell you what broke. They rarely tell you why. In this video, Serge walks through a real Next.js production bug that only affected Firefox and Safari. The error showed up clearly in Sentry, but the stack trace alone wasn’t enough to explain what was going wrong. The missing piece turned out to be logs. You’ll see how adding logs to a Next.js API route exposed unexpected request data, how those logs connected back to traces, and how that context made the root cause obvious and easy to fix.
Unity SDK 4.0.0: Console support, logs, user feedback and more
We just released the Sentry SDK for Unity 4.0.0 , our biggest update yet. This major release brings comprehensive gaming console support, structured logging, user feedback capabilities, and significant improvements to help you build better games across all platforms. Here's what's new.
Logs on Sentry in 60 seconds
Aggregate and query logs on Sentry. Add logs to your errors, errors to not only make debugging easier, but also give valuable context to Seer AI. Logs help you and Seer better understand issues.
Next.Js with Sentry in 60 seconds
Get started with Sentry for Next.js in just one minute.
Session Replay in 60 seconds
Learn about Sentry's Session Replay in 60 seconds.
Trace-connected structured logging with LogTape and Sentry
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 up. To build truly observable systems, we have to transition from simple text logs to structured, queryable, trace-connected events.