Sentry Hacktime with Bete and Cody
Today we will be implementing application Logs live.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Debugging and logging in Laravel applications
Logic errors, failed HTTP requests, background jobs that ghost silently—software breaks in all kinds of fun ways. The difference between resilient systems and fragile ones isn’t about avoiding errors altogether. It’s about how fast and clearly you can see what went wrong, and fix it. Laravel gives you a solid foundation: structured logging, real-time introspection, and built-in performance monitoring.
It broke... lets fix it with Sentry MCP and Seer
Real debugging starts in the editor where you're probably digging through the last commits wondering what random thing changed. Fortunately, you're probably using Sentry and it's going to give you that information. Sentry's MCP is the best way to bring all that context of what broke and how, into your editor so you can fix broken things faster. With Seer, you can bring in the root cause, and solution, and have tools like Cursor or Claude Code go fix it. We'll show you how.
Crash reporting for gaming consoles is now Generally Available
TL;DR: Error monitoring and crash reporting for all major gaming consoles is now generally available (plus, the v1.1 of our Unreal Engine SDK). Already convinced? Jump to the ‘What’s In The Release?’ section. Over a decade ago, a customer hacked Sentry into their PlayStation 3 games. Fast forward to today, Sentry now supports thousands of game developers across web, mobile, and desktop. The missing piece? Consoles. Developers asked for it. We built it.
SvelteKit observability just got 10x better, and we're here for it
The Svelte Team recently announced full observability and tracing support for SvelteKit! This is great news for SvelteKit and Sentry users, since Sentry is already compatible with the new feature! In addition, this is even greater news for the JavaScript ecosystem as a whole because SvelteKit just became the first ESM-based meta-framework to support instrumentation and tracing out of the box.
Logs are Generally Available (Still logs, just finally useful)
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 "trace connected" from day one. This let us ensure they were tightly connected to the actions and performance happening in your application, right where developers already go to investigate errors, performance, and latency issues. Now, Logs is out of beta and generally available to everyone.
Setting up Sentry logs
Sentry logs is now generally available for all users. Serge walks us through how to quickly set it up in a Next.js app.
The core KPIs of LLM performance (and how to track them)
A few months ago, I built an MCP server for Toronto’s Open Data portal so an agent could fetch datasets relevant to a user’s question. I threw the first version together, skimmed the code, and everything looked fine. Then I asked Claude: “What are all the traffic-related data sources for the city of Toronto?” The tool call fired. I got relevant results. And then I hit an error: “Conversation is too long, please start a new conversation.” I had only asked one question.