Documentation forPapertrail


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 local0

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.

Read more: log configuration option

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 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:

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.