Stop logging cron jobs to /dev/null
I often see cron jobs configured to pipe all output to /dev/null to get rid of it. Other times the emails cron sent are piling up and ignored due to alert fatigue.
Steven Rombauts
Web developer, DevOps practitioner and Open Source enthusiast.
I often see cron jobs configured to pipe all output to /dev/null to get rid of it. Other times the emails cron sent are piling up and ignored due to alert fatigue.
It can be difficult to make sense of the slow query log when investigating MySQL database performance. Fortunately, MySQL comes with a little tool to help you interpret those queries, called mysqldumpslow.
I regularly need to find out which queries are being executed while debugging or investigating application performance. I used to configure MySQL to log into a file and then search the output to see what’s happening.