Overview Production blows up, you open Kibana to search logs, and discover the critical Pod was OOM-killed 3 minutes ago—the old logs vanished with the container. This is extremely common in K8s environments: Pods are ephemeral, and logs can’t disappear with them. K8s log collection is fundamentally different from traditional VM environments. In a traditional setup, logs sit quietly in /var/log/ and you just SSH in to read them. In K8s, Pods can be scheduled to any node at any time, destroyed and recreated at will, with logs scattered across the entire cluster....

Overview It’s 2 AM and alerts are firing. Your service can’t connect to the database, curl times out, but ping to the IP works fine. Is it a network issue or an application issue? Nine times out of ten, it’s DNS resolution gone wrong. DNS resolution is the most fundamental yet most overlooked piece of Linux infrastructure. Nobody thinks about it until it breaks—and when it does, the entire system acts like it suddenly has amnesia: every domain becomes unrecognizable....

Overview 3 AM. Your alarm goes off. You log into the server and see a single line on the screen: Kernel panic - not syncing: Fatal exception. Then the system reboots. When you finally get back in, the crash scene is completely gone — no logs, no core dump, no call trace. You stare at systemd-logind: System is going down with nothing to work with. If you’ve been in ops for a few years, you’ve been there....

Overview When the database slows down, the business slows down. Every ops engineer has heard this, but honestly, not many teams do database monitoring right. I’ve seen too many teams whose database monitoring looks like this: Zabbix templates running decade-old metrics, only two alert rules — “CPU over 90%” and “disk full” — while connection count, lock waits, cache hit rate, replication lag, and other metrics that actually provide early warning are not being collected at all....

Overview It’s 2 AM. Your phone screams. The monitoring dashboard is a sea of red — core transaction P99 latency just hit 8 seconds, upstream services are timing out and circuit-breaking, and customer support chat is flooding with screenshots. You’re VPN-ing in while your brain runs at full speed: have we seen this scenario in a drill? Is it covered in the runbook? Do I remember the failover steps? If you’re still searching the wiki for documentation at this moment, it means one thing: your runbook was written but never practiced....

Overview You’re an ops engineer at a smart manufacturing company. The factory floor has 200 edge gateways, each running data collection and real-time quality inspection services. Previously deployed with bare Docker, every update meant writing scripts to SSH into each machine, pull images, and restart containers. Running through 200 machines took half an hour, with a few always failing due to network jitter. You think: isn’t this exactly what Kubernetes solves?...

Overview Have you ever encountered this situation: users report “the system is slow,” you open Grafana and check a bunch of dashboards—CPU is fine, memory is fine, network is fine—but users insist it’s slow. What you need at this point is not more metric dashboards, but a complete request trace—from the moment the user clicks a button to when the database returns results, showing exactly how long each hop took and where it got stuck....

Overview 3 AM, woken up by an alert. You log into the server and find a critical configuration file has been modified, but last shows no one logged in during that window, and bash_history has nothing. You know something happened, but you don’t know who did it or how. This is when you need auditd—the audit system built into the Linux kernel. It’s like an airplane’s black box, recording every critical action on the system: who executed what command, which files were accessed, what configurations were changed, and when privilege escalation occurred....

Overview Three ops engineers, 200 servers. Every morning: SSH into each one, check disk, memory, CPU, connection count, certificate expiry… the entire morning is gone. When a sudden outage hits, there is no time to inspect — the problem has already exploded in user complaints. This is not an isolated case. Many small-to-mid teams still do ops inspection the “manual + script” way — a few Shell scripts scattered across machines, unmaintained, nobody knows when they last ran, and nobody reads the output....

Overview Jenkins users fall into two camps: one fills out forms on the web UI, clicks a few buttons, and gets things running — simple and direct. The other writes Jenkinsfiles in the code repository, turning build pipelines into code with version control, peer review, and rollback all built in. The first is called Freestyle Project. The second is called Pipeline Project. These two aren’t mutually exclusive. Many teams use both — simple script tasks with Freestyle, complex multi-stage releases with Pipeline....