Blog

Posts tagged “OpenTelemetry”

AdonisJS monitoring and logging: three JSON request log lines from an AdonisJS 7 request logger middleware with request_id, route /api/v1/orders/:id and statuses 200, 500 and a 404 for /wp-login.php (illustrative)
Monitoring

AdonisJS monitoring and logging: the built-in logger, request logs and APM

AdonisJS ships a Pino logger and health checks but logs no requests and sends raw error messages on a 500. How to add request logs by route, metrics, OpenTelemetry tracing and a safer exception handler, tested on AdonisJS 7.

Jason Fill November 13, 2026 10 min read
hapi monitoring and logging: a hapi-pino log line with a redacted password, per-route metric counts for /v1/orders/{orderId} and /{p*}, and an OpenTelemetry route span, from a test run on hapi 21.4.13.
Monitoring

hapi monitoring and logging: hapi-pino, request lifecycle events and APM

hapi 21 gives you a hook for every layer of monitoring. Set up hapi-pino with redaction, per-route Prometheus metrics, Boom error logging and OpenTelemetry traces, with code we ran and the output it printed.

Jason Fill November 13, 2026 11 min read
Koa monitoring and logging header: a request log with route patterns and 200, 500 and 403 statuses, a prom-client duration counter for /v1/orders/:id, and an OpenTelemetry span named GET /v1/orders/:id, output from the article's samples on Koa 2.16.4 and 3.3.0.
Monitoring

Koa monitoring and logging: request logs, metrics and APM for Koa 2 and 3

A Koa timing middleware that only uses try/finally logs every crash as a 404. How to set up Koa logging with pino, per-route metrics with prom-client, error reporting and OpenTelemetry traces, tested on Koa 2 and 3.

Jason Fill November 13, 2026 11 min read
Fastify monitoring header: terminal showing an onResponse timing log, @fastify/otel spans for loadUser, handler and request, and an under-pressure 503 from a test run on Fastify 5.12.8
Monitoring

Fastify monitoring: hooks, metrics and APM for Fastify 4 and 5

Set up Fastify monitoring that shows which route got slow and why: onResponse timings, fastify-metrics histograms, @fastify/otel spans per hook, and under-pressure load shedding, with output from real runs.

Jason Fill November 13, 2026 10 min read
Header: 'Count the requests your interceptor never sees.' beside real /metrics output from a NestJS test app: middleware-recorded series for /api/users/:id with statuses 200, 403 (guard) and 400 (pipe) plus an unmatched 404, and a global interceptor that counted the same five requests as three 200s.
Monitoring

NestJS monitoring: metrics, APM and tracing that see guards and interceptors

NestJS monitoring that counts every request: per-route Prometheus metrics from middleware, OpenTelemetry tracing on NestJS 11 and 12, and what interceptors miss.

Jason Fill November 13, 2026 11 min read
ApiTraffic header: Express monitoring by route, not by URL, with a /metrics output panel listing route-labelled request counts for 200, 201, 404 and 500 responses
Monitoring

Express monitoring: route-level metrics, APM and alerts for Express 4 and 5

Most Express metrics are labelled by raw URL and miss async errors. Build route-level metrics with prom-client, add OpenTelemetry in the right load order, and set alerts, with code we ran on Express 4.22.3 and 5.3.0.

Jason Fill November 12, 2026 11 min read
Header: 'Node.js API monitoring: What to measure, how to set it up, and which tools fit a small team', with a metrics panel from the guide's example: /orders/:id p95 250ms and 2.0% 5xx, /report p95 250ms, unmatched 404, event loop delay p50 120.8ms against an idle 20.2ms.
Monitoring

Node.js API monitoring: what to measure, how to set it up, and which tools fit a small team

Uptime checks miss most of what breaks a Node API. What to measure per route and per process, a tested Express middleware for RED metrics and event loop delay, where OpenTelemetry fits, a fair tool comparison and the alerts worth paging on.

Jason Fill November 12, 2026 16 min read
Header: 'Observability for a 5-person Node team' with four cards: Errors (what threw, in which release), APM (what's slow, and why), OpenTelemetry (instrument once, send anywhere), Request log (who called, and what they sent).
Monitoring

Observability for a 5-person Node team: what each option actually gives you

When a customer says the export failed again, how long until you see the exact request? For most small Node teams the answer is spread across three tools. Here's what each option is built for, the gaps that bite, and a setup you can copy.

Jason Fill November 10, 2026 6 min read