Prerequisites
- A Bronto account and API key (how to create one)
- HAProxy logging to local syslog (
log 127.0.0.1 local0inhaproxy.cfg), with rsyslog writinglocal0to/var/log/haproxy.log - An OpenTelemetry Collector (recommended) or Fluent Bit installed on the same host
Configure the Collector
/etc/otel/config.yaml
<REGION> to eu or us. No rsyslog on the host? Receive HAProxy’s syslog stream directly with the OTel Collector’s syslog receiver instead of filelog.
What you will see in Bronto
Open Search and filter byservice.name = haproxy. The HTTP log format includes the client IP, the frontend and backend names, the chosen server, connection and response timers (queue, connect, response, total), the status code, bytes, and the session termination state. Bronto’s Custom Parser has built-in HAProxy support, so these fields are extracted automatically.
Troubleshooting
- No logs? Confirm
log 127.0.0.1 local0is set inhaproxy.cfgand that rsyslog routeslocal0.*to/var/log/haproxy.log, then restart both services. - For general issues, see OTel Collector troubleshooting.
Alternative: Fluent Bit
If you already run Fluent Bit, tail the HAProxy log file and forward it over HTTP:fluent-bit.conf
json_lines, not json. See Connect Fluent Bit to Bronto for installation.
