Nginx errors pile up fast
A single nginx error log can contain hundreds of lines — upstream timeouts, SSL handshake failures, permission denied, connection resets. Picking through them with tail and grep works for a quick check, but when you need to correlate errors across time or find patterns in rotated logs, the terminal gets tedious fast.
Downloading logs to a local editor works, but you lose the live connection and end up with stale copies. Cloud platforms want you to ship everything to their infrastructure first. You just want to look at your nginx errors and figure out what broke.