skills/nestjs/nestjs-observability/SKILL.md
Configure structured logging with Pino, Prometheus metrics, and health checks for NestJS services. Use when adding JSON logging, request tracing with correlation IDs, Prometheus metric endpoints, or liveness/readiness health checks.
npx skillsauth add hoangnguyen0403/agent-skills-standard nestjs-observabilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use nestjs-pino for high-performance, async JSON logging. Node's console.log blocking and unstructured.
See implementation examples
reqId. nestjs-pino handles this via AsyncLocalStorage.x-request-id to downstream microservices and database queries for end-to-end tracing.Expose /metrics for Prometheus scraping using @willsoto/nestjs-prometheus.
See implementation examples
TypeOrmHealthIndicator / PrismaHealthIndicator.X-Response-Duration-Ms, X-DB-Execution-Ms, X-API-Overhead-MsENABLE_PERFORMANCE_BENCHMARK feature flag; never expose in production.x-request-id header to all downstream services and queries.ENABLE_PERFORMANCE_BENCHMARK flag.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.