I'm not sure if I'm asking the right question here, but there's some guy that I work with who has a few years seniority on me that seems to know exactly where to look for any given log showing the problem. He then reads the exact relevant line from the log, and the problem is fixed.
^ that general description is what made me think of this question.
I'm aware of Android's Log.v(), Log.d(), Log.i(), Log.w(), and Log.e(). And Linux's common logs (feel free to make me aware of other relevant logs if they're not on this list)
/var/log/messages : General message and system related stuff
/var/log/auth.log : Authenication logs
/var/log/kern.log : Kernel logs
/var/log/cron.log : Crond logs (cron job)
/var/log/maillog : Mail server logs
/var/log/qmail/ : Qmail log directory (more files inside this directory)
/var/log/httpd/ : Apache access and error logs directory
/var/log/lighttpd/ : Lighttpd access and error logs directory
/var/log/boot.log : System boot log
/var/log/mysqld.log : MySQL database server log file
/var/log/secure or /var/log/auth.log : Authentication log
/var/log/utmp or /var/log/wtmp : Login records file
/var/log/yum.log : Yum command log file.
As I was writing this I gave it a quick search and found this https://cmatskas.com/an-introduction-to-common-logging-api-2/
Is there anything outside of this that I should know?