Configuring centralized logging from MySQL query logs
Aggregate logs from MySQL, including slow queries and error messages.
We recommend Papertrail's tiny standalone
remote_syslog daemon to read the
mysql-slow.log (and any other log files) in realtime.
Using remote_syslog is usually the way to go, since it requires no changes to MySQL, is easier to setup, and works for non-MySQL log files as well.
MySQL 5.1.20 and later can also use its own native syslog
support plus the system-wide syslog daemon (Method B). To see which version of MySQL is
That's not available in MySQL 5.1.19 and earlier and it's more work to setup, so we recommend remote_syslog (A).
1. Install remote_syslog.
sudo gem install remote_syslog
another location). Edit it to define:
- path to your MySQL slow query log file (such as
/var/log/mysql/slow_queries.log), error log file (such as
/var/log/mysqld.log), and any other log files which remote_syslog should watch.
- destination hostname and port provided by Papertrail's Web interface. If no destination port was provided, remove that config line to use the default (514).
Start the daemon:
MySQL versions 5.1.20 and later support logging to syslog
natively. Two arguments to mysqld_safe control logging:
Both, either, or neither argument can be used. mysqld_safe is
generally started from
/etc/init.d/mysqld. Edit that
file (or its equivalent for your distribution) and confirm that
--syslog is included on the command line, or add
Here is a sample which makes MySQL log to syslog and directly to a file:
/usr/bin/mysqld_safe --datadir="$datadir" --socket="$socketfile" \ --syslog --log-error="/var/log/mysql.err" --pid-file="$mypidfile" \ >/dev/null 2>&1 &