Operations | Monitoring | ITSM | DevOps | Cloud

Building with Next.js and using Sentry? Our team put together a dedicated Next.js Overview Dashboard that gives you a full picture of your application's health, not just errors. Out of the box, the dashboard covers page loads, API latency, issue counts, performance scores, rage and dead clicks, and slow SSR. Since Next.js runs on both client and server, you get a breakdown of client transactions, server transactions, and your SSR file tree all in one place.

Most observability stacks aren’t designed, they accumulate. A logging tool here, a tracing platform there, and before you know it you’re managing rising costs and a setup that ultimately slows down your team. And you’ve moved further away from actually solving problems for your users.

Cursor Automations + Sentry Triggers: go from user feedback to a pull request automatically. See how to set up an end-to-end workflow that turns feedback into code changes, posts the PR to Slack, and keeps your team in the loop. In this video, we walk through a real-world example using Sentry Docs. A user submits feedback through a widget on the docs site, it lands in Sentry as an issue, and when assigned, a Cursor Automation kicks off. The automation reads the feedback, validates it, generates a PR against the repo, and posts the link in the relevant Slack thread. No manual work required.

We released a new type of dashboard widget - Text Widgets! You can use them to explain other widgets (good for onboarding), or even define your playbooks - instructions on how to investigate failures by reading the other widgets. They even support markdown!