Ian Wienand f97b9b8b8b haproxy: redirect logs to a separate file
haproxy only logs to /dev/log; this means all our access logs get
mixed into syslog.  This makes it impossible to pick out anything in
syslog that might be interesting (and vice-versa, means you have to
filter out things if analysing just the haproxy logs).

It seems like the standard way to deal with this is to have rsyslogd
listen on a separate socket, and then point haproxy to that.  So this
configures rsyslogd to create /var/run/dev/log and maps that into the
container as /dev/log (i.e. don't have to reconfigure the container at
all).

We then capture this sockets logs to /var/log/haproxy.log, and install
rotation for it.

Additionally we collect this log from our tests.

Change-Id: I32948793df7fd9b990c948730349b24361a8f307
2022-07-07 21:29:13 +10:00
..
2021-06-02 13:56:19 +10:00
2020-02-12 16:39:11 +11:00
2022-05-05 08:36:20 -07:00
2020-11-20 19:13:32 +11:00
2022-04-20 16:47:02 -07:00
2022-03-10 12:49:56 +11:00
2020-11-05 11:56:46 +11:00
2020-04-16 12:45:36 -05:00
2022-01-19 11:00:12 -08:00
2022-05-04 13:08:28 -07:00
2020-10-19 14:06:57 +11:00
2022-06-09 16:37:54 +10:00
2018-08-23 21:34:42 +10:00
2022-02-01 13:52:47 -08:00
2022-02-01 13:52:47 -08:00
2021-12-13 14:54:16 +11:00