DevOps and Observability
Focused devops and observability articles with clear context, practical examples, source links where needed, and honest limits.
5 articles in this section.
Docker provenance for Node.js images: what a deploy should prove
A deployment should identify the source revision, dependency inputs, image digest, and build environment. Provenance makes that chain inspectable when a...
OpenTelemetry sampling: keep rare failures without storing everything
Tracing every request can be expensive, while sampling away every rare failure makes debugging impossible. A useful policy keeps errors, slow requests, ...
Docker image supply chain: lockfiles, provenance, and runtime users
A container image is also a dependency bundle and a release artifact. Secure builds need reproducible inputs, a small runtime, useful provenance, and a process
OpenTelemetry for Node.js: the first traces a small team should collect
Observability becomes useful when it answers a specific question. A small Node.js team can start with request traces, dependency timing, and error context inste
Docker for Node.js: a production checklist beyond the first container
A plain-language Docker checklist for Node.js applications covering image size, permissions, health checks, signals, environment variables, and reproducible builds.