Make Your Logs Work for You
The days of logging in to servers and manually viewing log files are over. SolarWinds® Papertrail™ aggregates logs from applications, devices, and platforms to a central location.View Technology Info
Troubleshoot Fast and Enjoy It
SolarWinds® Papertrail™ provides cloud-based log management that seamlessly aggregates logs from applications, servers, network devices, services, platforms, and much more.View Capabilities Info
Aggregate and Search Any Log
SolarWinds® Papertrail™ provides lightning-fast search, live tail, flexible system groups, team-wide access, and integration with popular communications platforms like PagerDuty and Slack to help you quickly track down customer problems, debug app requests, or troubleshoot slow database queries.View Languages Info
Meet the Event Viewer
It's the heart of Papertrail.Start Tour
TAKE A TOUR
TBD - APM Integration Title
TBD - APM Integration DescriptionTBD Link
APM Integration Feature List
TBD - Built for Collaboration Title
TBD - Built for Collaboration DescriptionTBD Link
Built for Collaboration Feature List
Collect Logs: Apps & Services
Collect Logs: Hosting Services
Collect Logs: Integrations
Send Logs for Analytics
SolarWinds Users & Orgs
Support and Security
Aggregate logs from MySQL, including slow queries and error messages.
We recommend Papertrail’s tiny standalone
remote_syslog2 daemon to read the
mysql-slow.log (and any other log files) in realtime (remote_syslog2). 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 (Native). To see which version of MySQL is installed, run:
The native method is not available in MySQL 5.1.19 and earlier.
Download the current release. To extract it and copy the binary into a system path, run:
$ tar xzf ./remote_syslog*.tar.gz
$ cd remote_syslog
$ sudo cp ./remote_syslog /usr/local/bin
RPM and Debian packages are also available.
Paths to log file(s) can be specified on the command-line, or save log_files.yml.example as
/etc/log_files.yml. Edit it to define:
/var/log/mysql/slow_queries.log), error log file
/var/log/mysqld.log), and any other log files that remote_syslog2 should watch.
port provided under log destinations. If no
destination port was provided, set
logs.papertrailapp.com and remove the
port config line to use the default port (514).
The remote_syslog2 README has complete documentation and more examples.
Start the daemon:
$ sudo remote_syslog
Logs should appear in Papertrail within a few seconds of being written to the on-disk log file. Problem? See Troubleshooting.
remote_syslog requires read permission on the log files it is monitoring.
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 it.
Here is a sample that sends MySQL logs 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 &
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.