Observability built for NestJS by its creator. Add the SDK and a key, and every request shows up as a trace of your own controllers, providers and queries, with errors, jobs, logs and runtime metrics alongside. Free up to 300k events a month.
Hey Product Hunt! I'm Kamil, I created NestJS.
Over the years we've seen thousands of NestJS projects that never got as far as monitoring. The tools took too much setup for what they showed (a POST /orders and a database call, with nothing in between), or they cost too much. So we built observability that understands Nest.
Add @nestjs/observe (or say yes when nest new asks) and an API key. From there, without writing a single span:
Tracing
- every request and job as a waterfall of your own controllers, providers, guards and pipes, with the database queries underneath
- distributed tracing across HTTP, microservices and GraphQL, so a request that fans out stays one trace
- a service map of how your applications call each other
- own time vs total time per class and method, so you find the real bottleneck
Errors, issues and releases
- errors with the failing source code inline, grouped into defects, plus an email when a new one appears
- turn any error, trace or job into an issue with an owner, severity and due date
- every request is tagged with the release that served it: compare releases by errors and latency, see which deploy brought a regression, and resolved issues reopen if the failure comes back
Jobs and runtime
- BullMQ jobs and cron runs, with queue wait time and retries
- CPU, memory, event loop and garbage collection per instance
- your own counters and gauges, and per-user activity
Logs and alerts (Pro)
- logs on the trace timeline, tied to the request that wrote them, redacted by default
- alerts on thresholds, anomalies, log patterns and silence (an app that stops getting traffic, a cron that never runs), to email, Slack, webhooks or issues
- SLOs with error budgets and burn-rate alerts (Scale)
For your coding agent
- one click turns a failure into a prompt for Claude Code or Cursor, and an MCP server (Pro) lets the agent query your telemetry directly
It covers HTTP, GraphQL, microservices (all built-in transports) and WebSockets. Nothing is sent on the request path; a worker thread ships the data in the background. The SDK is MIT on GitHub, and the dashboard is hosted. It won't replace a big Datadog setup across many languages, and it doesn't cover the frontend.
Free up to 300k events a month, no card. The live demo needs no signup: https://www.observe-demo.nestjs....
I'll be here all day. What should we build next?
Nice that NestJS Observe is zero-config, so I can get real tracing on a NestJS app without wiring up half a dozen exporters first.
About NestJS Observe on Product Hunt
“Zero-config observability built for NestJS”
NestJS Observe launched on Product Hunt on October 15th, 2026 and earned 74 upvotes and 4 comments, placing #28 on the daily leaderboard. Observability built for NestJS by its creator. Add the SDK and a key, and every request shows up as a trace of your own controllers, providers and queries, with errors, jobs, logs and runtime metrics alongside. Free up to 300k events a month.
NestJS Observe was featured in Analytics (174.2k followers), Software Engineering (43.2k followers) and Developer Tools (521.3k followers) on Product Hunt. Together, these topics include over 114k products, making this a competitive space to launch in.
Who hunted NestJS Observe?
NestJS Observe was hunted by Kamil Myśliwiec. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how NestJS Observe stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Kamil Myśliwiec