by NestJS Kamil MysliwiecCommunityAsk about your NestJS app in production: errors with their traces and logs, slow endpoints, failing jobs, and what the last release changed.
NestJS Observe is the observability platform from the makers of NestJS. This connector lets AgentOne work from your application's real production data instead of guessing from the code.
Ask AgentOne what regressed after the last deploy. It compares error rates and latency on either side of each release, then shows what the bad release changed in the code: a new N+1 query, an added outbound call, or a slower method. Ask about an error, and AgentOne can return the error group, its occurrences, the full trace waterfall across services, and the log lines written while it happened. AgentOne can also find the slowest endpoints, failing background jobs, the users an error reached, burning SLOs and firing alerts, and where the time goes in each NestJS class and method.
Every answer covers only the projects you can see, with your permissions, and ends with links to the dashboard pages it came from. Almost every tool only reads. The few that write create a project, an application or an API key, to set up a new service, or mark an issue resolved once a fix ships. Nothing can be deleted or edited otherwise.
You need a NestJS Observe account with an application reporting through the @nestjs/observe SDK. MCP is included on the Pro plan and above.