🔭 Your NestJS app is more than your code, so NestJS Observe tracks more than your code:
🐘 Every SQL query
🌍 Every outbound HTTP call
🗺️ A map of how it all connects
📧 An email the first time something breaks
None of it configured 👇
🧬 A spike of 3,140 TypeErrors is one bug, not 3,140 of them.
Flip on defect grouping and the same exception class with the same stack shape collapses into one group - fingerprinted server-side, however the message was worded or which deploy produced it.
🔔 Alerts on thresholds or anomalies, absence detection, log patterns, queue waits, quiet hours.
🎯 SLOs with error budgets and burn-rate alerts.
🤖 A read-only MCP server your agent can query.
✅ Errors and tracing on every plan, free tier included.
👋 @nestframework community, we’ve been looking forward to sharing this with you
If you’ve used Prisma in NestJS, a few things will look different this time.
Here’s the new way to build with Prisma ORM 8 ↓
pris.ly/nestjs-blog
🗺️ New in NestJS Observe: the Service Map.
Every application, queue, database and external API in your project, connected by the calls they actually made. How busy, how slow, what's failing.
Built from your traffic. Nothing to draw or configure.
observe.nestjs.com
NestJS v12.1.0 is out 🎉
🗄️ @nestjs/drizzle, the official Drizzle ORM integration
🛡️ Built-in CSRF protection and security headers
🍪 Built-in cookies, including signed cookies
📎 File uploads on the Fastify adapter
github.com/nestjs/nest/relea…
📨 New in NestJS Observe: an email the moment a new unhandled error appears in your project. On every plan, with a toggle to switch it off.
Plus the headers (and optionally the body) of failed or slow requests, redacted before they leave your process.
observe.nestjs.com
How do you monitor a NestJS app in production? 🎯
What’s actually worth watching, what each signal tells you, and how to get full observability without spending a week wiring everything together.
dev.to/nestjs/how-to-monitor…
🔎 How to monitor a NestJS app
🎯 What's worth watching in a NestJS app in production, what each signal actually tells you, and how to get all of it without spending a week on plumbing.
dev.to/nestjs/how-to-monitor…
🛢️ @nestframework Observe now shows the SQL behind a slow request.
Every query is a row in the trace, under the method that ran it. TypeORM, Drizzle, MikroORM, Mongoose. Zero setup.
Values are never sent. Query spans aren't billed.
observe.nestjs.com/
Also in there: performance outliers ranked against budget, top routes by volume, open issues tied to real error groups, and background job success/failure tracking.
If you're building on NestJS and curious what "zero-config observability" actually looks like day one - this is it. Feedback welcome.
observe.nestjs.com/