For MOS 6.1, HAProxy logs to /var/log/haproxy.log or /var/log/messages: it all depends on the way Puppet ordered the resources during the deployment of the environment and it can't be predicted. The following workaround will work in all cases for MOS 6.1.
Workaround
==========
Edit /etc/lma_collector/logstreamer-system.toml and modify this line:
This issue is related to this upstream bug: https:/ /bugs.launchpad .net/fuel/ +bug/1481860
For MOS 6.1, HAProxy logs to /var/log/ haproxy. log or /var/log/messages: it all depends on the way Puppet ordered the resources during the deployment of the environment and it can't be predicted. The following workaround will work in all cases for MOS 6.1.
Workaround
==========
Edit /etc/lma_ collector/ logstreamer- system. toml and modify this line:
file_match = '(?P<Service> daemon\ .log|cron\ .log|kern\ .log|auth\ .log|syslog| messages| debug)'
to this:
file_match = '(?P<Service> daemon\ .log|cron\ .log|kern\ .log|auth\ .log|syslog| messages| debug|haproxy\ .log)'