1.2 KiB
1.2 KiB
AGENTS.md
Production data: NestJS Observe
This app's production telemetry - traces, errors, logs and metrics - goes to NestJS Observe. Until ObserveModule is registered in src/app.module.ts, nothing is sent: npx @nestjs/observe link sets it up in one step - it installs @nestjs/observe, wires it into the app, and writes the key pair (OBSERVE_APP_KEY, OBSERVE_APP_SECRET) to .env.
When a task depends on how the app behaves in production - an error users hit, a slow endpoint, a failing job, whether a release made things worse - work from that data, not from the code alone:
- The Observe MCP server answers those questions directly: errors with their traces and logs, slow operations, jobs, and what a release changed (
find_regressions,diff_release). It is included on the Pro plan and above. In Claude Code:claude mcp add observe --transport http https://observe-api.nestjs.com/mcp, and the client opens a browser to approve. Other clients: https://www.observe.nestjs.com/documentation/mcp - Without it, the user can open the request or error in the Observe dashboard and click Copy agent prompt, which hands over that page's trace, stack and logs as text.