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

FEATURED TECHNOLOGY

Kubenetes Cluster Logging Kubernetes Logging AWS Log Management GC Log Analyzer AWS Logging Docker Logging Docker Syslog Heroku Logging Logging Tools for Azure App

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

FEATURED CAPABILITIES

Log Viewer Firewall Log Analyzer Centralized Log Management Log Analysis Tail Logging Cron Job Monitoring Log Aggregator Cloud Logging

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

FEATURED LANGUAGES

Linux Logging Software Linux Log Management Ruby Logging Manager Golang Logging HAproxy Log Analyzer MySQL Logging NGINX Logging Javascript Logging Tomcat Logging Apache Log Analyzer

Administrator Guide
- Documentation for Papertrail
Collect Logs
Collect Logs: Apps & Services
Collect Logs: Hosting Services
Collect Logs: Integrations
- Fluentd
- Librato
- Amazon CloudWatch
- StatHat
- Amazon SNS
- HostedGraphite
- Datadog
- Zapier
- VictorOps
- New Relic traces
- Slack
- Campfire
- PagerDuty
- New Relic Insights
- Pushover
- AppOptics
- Geckoboard
- OpsGenie
- Honeybadger
Manage Logs
Send Logs for Analytics
SolarWinds Users & Orgs
Support and Security
- Security and Compliance
- Support Policy
What's New
- Papertrail Release Notes

haproxy

Aggregate logs from haproxy, a “reliable, high Performance TCP/HTTP load balancer,” including HTTP requests and errors.

Direct logging

haproxy supports remote syslog natively, so it can log directly to Papertrail. Edit haproxy.cfg and add a new global log configuration option like this, as well as log-send-hostname:

log logsN.papertrailapp.com:XXXXX local0
log-send-hostname

where logsN and XXXXX are the name and port number shown under log destinations.

Second, add log global to each server’s configuration stanza to indicate that it should use the aforementioned configuration.

haproxy supports up to 2 concurrent log configuration outputs.

Define syslog tag and/or hostname (optional)

Syslog messages include a program name (“tag”) and sender identifier (“hostname”). With the configuration above, haproxy will use default values of haproxy and the system hostname. These are typically fine.

Changing the tag is typically only necessary if you run multiple haproxy instances on the same system. Use different tag values to tell their logs apart.

Changing the hostname is rarely needed, since the system hostname is usually the best identification.

To change them, use the log-tag or log-send-hostname options.

Change logging verbosity (optional)

Optionally append a minimum severity from among the set:

log logsN.papertrailapp.com:XXXXX local0 warning

where logsN and XXXXX are the name and port number shown under log destinations.

Alternatives: local log file or system syslog

If you do not want to have haproxy log directly to Papertrail, you can use one of these two methods instead:

have haproxy log to a standalone text log file and transmit that to Papertrail. See Configuring centralized logging from text log files in Unix with remote_syslog2.
have haproxy log to the system’s syslog daemon and use that to transmit to Papertrail. See Configuring remote syslog from Unix/Linux and BSD/macOS.

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.