How do I install the Nestjs Observability skill?

Run npx skillmds@latest add comeonoliver/nestjs-observability in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nestjs Observability safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nestjs Observability?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nestjs Observability free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nestjs Observability?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nestjs Observability by comeonoliver

Name: Nestjs Observability
Rating: 4.666666666666667 (3 reviews)
Author: ComeOnOliver

Nestjs Observability

Structured logging (Pino) and Prometheus metrics. Use when adding structured logging with Pino or Prometheus metrics to NestJS services. (triggers: main.ts, **/*.module.ts, nestjs-pino, Prometheus, Logger, reqId)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Observability Standards

Priority: P1 (OPERATIONAL)

Logging, monitoring, and observability patterns for production applications.

Standard: Use nestjs-pino for high-performance JSON logging.
- Why: Node's built-in console.log is blocking and unstructured.
Configuration:
- Redaction: Mandatory masking of sensitive fields (password, token, email).
- Context: Always inject Logger and set the context (LoginService).

Tracing (Correlation)

Request ID: Every log line must include a reqId (Request ID).
- nestjs-pino handles this automatically using AsyncLocalStorage.
- Propagation: Pass x-request-id to downstream microservices/database queries key to trace flows.

API Overhead & Database Benchmarking

Execution Bucket Strategy: When performance profiling is enabled, utilize global interceptors combined with AsyncLocalStorage to split and expose latency into logical buckets.
Headers: Expose the metrics via HTTP Headers on the response for immediate feedback during development or testing:
- X-Response-Duration-Ms (Total execution time)
- X-DB-Execution-Ms (Time spent exclusively in database queries, tracked via TypeORM loggers)
- X-API-Overhead-Ms (Time spent in NestJS interceptors, guards, and serialization)
Security: Only enable performance headers and detailed SQL benchmarking in development or when a specific feature flag (ENABLE_PERFORMANCE_BENCHMARK) is explicitly active.

Metrics

Exposure: Use @willsoto/nestjs-prometheus to expose /metrics for Prometheus scraping.
Key Metrics:
1. http_request_duration_seconds (Histogram)
2. db_query_duration_seconds (Histogram)
3. memory_usage_bytes (Gauge)

Health Checks

Terminus: Implement explicit logic for "Liveness" (I'm alive) vs "Readiness" (I can take traffic).
- DB Check: TypeOrmHealthIndicator / PrismaHealthIndicator.
- Memory Check: Fail if Heap > 300MB (prevent crash loops).

Anti-Patterns

No console.log: Use nestjs-pino for async, structured, JSON-formatted logging.
No missing reqId: Propagate x-request-id header to all downstream services and queries.
No perf data in production by default: Gate benchmarking behind ENABLE_PERFORMANCE_BENCHMARK flag.

---name: nestjs-observabilitydescription: Structured logging (Pino) and Prometheus metrics. Use when adding structured logging with Pino or Prometheus metrics to NestJS services. (triggers: main.ts, **/*.module.ts, nestjs-pino, Prometheus, Logger, reqId)---# Observability Standards## **Priority: P1 (OPERATIONAL)**Logging, monitoring, and observability patterns for production applications.- **Standard**: Use `nestjs-pino` for high-performance JSON logging. - **Why**: Node's built-in `console.log` is blocking and unstructured.- **Configuration**: - **Redaction**: Mandatory masking of sensitive fields (`password`, `token`, `email`). - **Context**: Always inject `Logger` and set the context (`LoginService`).## Tracing (Correlation)- **Request ID**: Every log line **must** include a `reqId` (Request ID). - `nestjs-pino` handles this automatically using `AsyncLocalStorage`. - **Propagation**: Pass `x-request-id` to downstream microservices/database queries key to trace flows.## API Overhead & Database Benchmarking- **Execution Bucket Strategy**: When performance profiling is enabled, utilize global interceptors combined with `AsyncLocalStorage` to split and expose latency into logical buckets.- **Headers**: Expose the metrics via HTTP Headers on the response for immediate feedback during development or testing: - `X-Response-Duration-Ms` (Total execution time) - `X-DB-Execution-Ms` (Time spent exclusively in database queries, tracked via TypeORM loggers) - `X-API-Overhead-Ms` (Time spent in NestJS interceptors, guards, and serialization)- **Security**: Only enable performance headers and detailed SQL benchmarking in development or when a specific feature flag (`ENABLE_PERFORMANCE_BENCHMARK`) is explicitly active.## Metrics- **Exposure**: Use `@willsoto/nestjs-prometheus` to expose `/metrics` for Prometheus scraping.- **Key Metrics**: 1. `http_request_duration_seconds` (Histogram) 2. `db_query_duration_seconds` (Histogram) 3. `memory_usage_bytes` (Gauge)## Health Checks- **Terminus**: Implement explicit logic for "Liveness" (I'm alive) vs "Readiness" (I can take traffic). - **DB Check**: `TypeOrmHealthIndicator` / `PrismaHealthIndicator`. - **Memory Check**: Fail if Heap > 300MB (prevent crash loops).## Anti-Patterns- **No console.log**: Use nestjs-pino for async, structured, JSON-formatted logging.- **No missing reqId**: Propagate `x-request-id` header to all downstream services and queries.- **No perf data in production by default**: Gate benchmarking behind `ENABLE_PERFORMANCE_BENCHMARK` flag.

Frequently asked questions