Explore tools for infrastructure operations, from monitoring software and API clients to Linux utilities, Git and runtime versions. Find comparisons, setup guidance and practical troubleshooting steps.
DevOps tools
The change looks harmless: a path adjustment, a new virtual host, a certificate renewal. It goes out after hours, the reload command returns, and the site appears to be up. Then requests start failing because the certificate file was moved earlier that day. NGINX can't use the new
DevOps tools
A gateway timeout means an intermediary server, such as a reverse proxy or load balancer, failed to receive a timely response from its upstream origin, so the client receives HTTP 504. The code has a formal specification milestone in RFC 7231, published on 2014-06-06, and the same definition remains in
observability
At 3 a.m., an on-call engineer is rarely looking at one screen. A latency alert opens Grafana, an application error requires a log search, a trace lives in a separate APM console, and a customer-facing outage still needs confirmation from an uptime service. The incident isn't difficult
network monitoring
A production application can look perfectly healthy while a portion of its audience sees timeouts, stale answers, or a completely unreachable hostname. The origin responds, the load balancer passes health checks, and the application dashboard stays green, yet a recursive resolver fails, one authoritative nameserver returns an incorrect record, or
DevOps tools
A deployment job fails after a clean checkout. The parent repository is present, but a directory that should contain shared code is empty. A second command initializes the immediate submodule, yet the build still breaks because that repository contains another submodule several layers deeper. The failure looks like an application
observability
Fewer tools don't automatically produce better operations. A team can remove dashboards, cancel contracts, and still make incidents harder to diagnose if the migration breaks proven integrations, hides important context, or forces engineers to relearn every workflow at once. Tool consolidation works when it reduces decisions and handoffs,
server monitoring
At 3:00 AM, an on-call engineer gets paged for elevated CPU. Grafana shows several spiking hosts, Prometheus has a dense set of time series, and UptimeRobot says one endpoint is intermittently unavailable. The engineer opens a separate log search, checks a deployment channel, and tries to determine whether the
incident response
Replacing Opsgenie isn't just a matter of choosing another paging product. Alert sources, escalation rules, schedules, notification channels, APIs, Terraform workflows, status communication, and the surrounding monitoring stack all have to keep working when the switch happens. The decision also has a hard deadline: Atlassian stopped new Opsgenie
DevOps tools
A 413 on a file upload usually arrives at the worst possible time. The form looked fine, the backend was deployed, the payload wasn't strange, and yet the browser or API client gets blocked before the request finishes. In practice, Request Entity Too Large is less about broken
DevOps tools
A developer opens a terminal, runs node -v, and realizes the runtime on the laptop, CI image, or production host is older than the app has grown around. That moment usually turns into a bigger question than “what command should be used,” because Node updates can change how dependencies install,
DevOps tools
A stale lockfile has a way of looking healthy right up until it hurts someone else. A developer runs npm install, the app boots, the tests pass, and the repo feels current enough, but a few packages are still behind the registry and one later upgrade lands with a breaking
DevOps tools
A deployment is live, the page loads, and then Nginx throws 403 Forbidden instead of serving the file. The site isn't dead, the server isn't down, and the request didn't disappear into the network. Nginx is telling you the request reached it, but something