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?

NestJS Observe

Zero-config observability built for NestJS

Zero-config observability built for NestJS