Reading nginx error logs without losing your mind
Most lines in a busy error.log are noise: clients that went away, scanners asking for /wp-login.php, TLS handshakes from bots with ancient ciphers. A short awk that strips the timestamp and client address and counts the rest shows the three messages that actually matter.
awk -F'] ' '{print $3}' error.log | sed 's/client: [^,]*,//' | sort | uniq -c | sort -rn | headUpstream timeouts and too many open files are the ones to act on. Everything else can go to a lower log level.