When a service is down, the first five minutes should be boring. A short checklist keeps the investigation grounded.
Check the unit
systemctl status my-service --no-pager -l
When a service is down, the first five minutes should be boring. A short checklist keeps the investigation grounded.
systemctl status my-service --no-pager -l
journalctl is one of the fastest ways to understand what a small server is doing.
journalctl -u my-service --since "30 minutes ago" --no-pager
TLS certificates should be quiet infrastructure. They only become interesting when renewal fails.
Before issuing a certificate, confirm the domain points to the expected host:
dig example.com A
Reverse proxies are simple in diagrams and detailed in production.
Most applications need the original host, scheme, and client address:
Host
X-Forwarded-For
X-Forwarded-Proto
SQLite is often treated as a prototype database, but it is a very practical choice for many internal tools.
Small systems do not need a huge monitoring stack to become easier to operate. They need a few consistent signals.
Logs should answer what happened, when it happened, and which request or job was involved.
Start with request count, error count, latency, queue length, process memory, and disk usage.
Flybug Notes is a compact technical notebook about small production systems.
The site focuses on Linux operations, backend habits, networking details, and tools that keep servers easier to understand.
Notes are grouped by topic. The goal is practical, compact writing that feels like a real engineering notebook.