Operations | Monitoring | ITSM | DevOps | Cloud

Retail stores have long relied on a secret weapon to measure and improve the shopping experience: the secret shopper. Posing as ordinary customers, they evaluate the customer experience, spotting friction points like hard-to-find items, gauging the quality of customer service, and testing how seamless the checkout process feels.

This could’ve been prevented. This should have been prevented. This too. We all hate getting tagged in PRs. The time, the blame for when you inevitably miss something, and constant “I wouldn’t have written it that way” feeling is just hard to shake. LLMs promised this would get easier. Promised they would do it for us. But as we’ve seen, we’re not there yet. But this is what Sentry does for a living. We catch bugs… in prod.

Dan Mindru is a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CronTool. I find it remarkable that we’re getting so many AI startups every day. As software engineers, most of us like to know what our software is actually doing. We plan, review, and perform automatic tests to verify it’s working as expected. Then we do a round of manual testing for good measure. Not with AI.

When a page pauses for even a quarter-second users feel it, and many will tab away before the spinner stops. Front-end performance testing lets us spot those delays on our own machines instead of reading about them in support tickets. The browser runs JavaScript, layout, painting, and every user interaction on a single main thread. If one task takes too long, everything else queues up behind it.

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 helps us validate what’s working, spot what’s missing, and catch issues we wouldn’t always see through error tracking alone.

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.

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.

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.

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.