----------------original message----------------- De: "Emeric BRUN" [email protected] A: "Dave Shevett" [email protected], [email protected] Date: Wed, 25 Sep 2013 08:37:22 +0200 ------------------------------------------------- > > > ----------------original message----------------- > De: "Emeric BRUN" [email protected] > A: "Dave Shevett" [email protected], [email protected] > Date: Wed, 25 Sep 2013 08:32:40 +0200 > ------------------------------------------------- > > >> >> >>> Hi everyone, we're to the point of needing to stop logging all >>> 'successful' hits via haproxy, but I can't seem to get the right mix of >>> configs to make it happen. Right now all hits, even successful ones, >>> are being logged. >>> >>> Here's the relevant portions of the haproxy.cfg file. Note we're >>> running 1.4.18. >>> >>> global >>> maxconn 16384 >>> user haproxy >>> group haproxy >>> daemon >>> >>> defaults >>> retries 3 >>> option redispatch >>> maxconn 8192 >>> contimeout 6000 >>> clitimeout 300000 >>> srvtimeout 300000 >>> balance roundrobin >>> >>> cookie HASRVID insert indirect nocache >>> >>> # Application listener - this is for the i-ready application itself >>> frontend http_proxy >>> log 10.10.1.177 local0 warning >>> option dontlognull >>> option dontlog-normal # turn off logging of regular, ie 'not >>> abnormal' traffic >>> option httplog >>> option log-separate-errors >>> >>> Her'es the log entries we're still seeing: >>> >>> Sep 24 16:42:55 stg-lb-1 haproxy[13367]: 54.243.31.199:28682 >>> [24/Sep/2013:16:42:55.298] http_proxy app/stg-2 2/0/1/6/11 200 >>> 11498 - >>> - >>> CDNI 2/2/2/0/0 0/0 "GET / HTTP/1.1" >>> >>> We'd like thos filtered out, but 404, 500's, other connect errors to >>> still log. >>> >>> Help please? >> >> Try to set it also in your backend section. > > Sorry, i've just read manual, and option seems not available on backend > section. You may found a bug. >
Option dontlog-normal seems to interact with the option log-separate-errors, you should retry removing this last option (if you can).
