What problem does it solve? Node.js services often run blind in production: slow Prisma queries, failing BullMQ jobs, and scattered logs with no way to connect them to a single request. This Skill sets up a complete OpenTelemetry pipeline so every request, database query, queue job, and log line is correlated and visible in your observability backend. ## Core Features & Use Cases - Auto-instrumentation setup: Generates instrumentation.ts with the OTel NodeSDK, auto-instrumentations for Fastify, HTTP, and Prisma, loaded before all other imports so nothing is missed. - Custom spans and queue tracing: Adds business-logic spans and propagates trace context from BullMQ producers to workers so async jobs stay connected to their originating request. - RED metrics and correlated logs: Configures rate/error/duration histograms per route and a Pino logger that injects traceId and spanId into every log line. - Use Case: You notice intermittent slow API responses in production. After running this Skill, you open SigNoz, find the slow trace, and see exactly which Prisma query or BullMQ job caused the delay. ## Quick Start Ask the AI to add OpenTelemetry tracing, RED metrics, and structured logging to your Fastify and Prisma service, exporting to your preferred backend such as SigNoz, Grafana, Jaeger, or Datadog.
