Re: unique-id-header logged twice ?

> On Aug 23, 2016, at Aug 23, 5:43 PM, Jakov Sosic wrote: > > Hi guys, > > > Later I log it in Apache in custom log format: > > LogFormat "%a %l %u [%{%d/%b/%Y:%T}t,%{msec_frac}t %{%z}t] \"%r\" %>s %b > \"%{Referer}i\" \"%{User-Agent}i\" \"%{X-Unique-ID}i\""

unique-id-header logged twice ?

Hi guys, I have following setings in my haproxy: defaults # populate X-Unique-ID header unique-id-format %{+X}o\ %ci:%cp_%fi:%fp_%Ts_%rt:%pid unique-id-header X-Unique-ID Later I log it in Apache in custom log format: LogFormat "%a %l %u [%{%d/%b/%Y:%T}t,%{msec_frac}t %{%z}t]

McKesson Business Contacts

Hello there, Might want to know whether you are keen on obtaining McKesson Business Contacts for your marketing effort. Specialties: Pharmaceutical Distribution, HealthCare IT, Practice Management, Supply Chain Management and many more... Please review and let me know your thoughts. Last

Re: Reflexions around timers in the logs

OK so I'm going to merge this now, it looks quite good and proves much more useful even in testing than what we've been dealing with over the last few years. If anybody wants to suggest a change, don't worry, we're still in development, we can change it later. Thanks for your comments! Willy ---

Re: Reflexions around timers in the logs

Hi guys, First, thanks a lot, that's *exactly* the type of feedback I was waiting for. On Tue, Aug 23, 2016 at 12:40:58PM +0200, Olivier Doucet wrote: > 2016-08-23 12:22 GMT+02:00 Conrad Hoffmann : (...) > > So with that reasoning, I guess I would love to see: > > - all

Re: Reflexions around timers in the logs

Hi all, 2016-08-23 12:22 GMT+02:00 Conrad Hoffmann : > Hi, > > first of all, it's great that this is being tackled. Thanks a lot! > > I don't have a very strong opinion on most of the details, but my thoughts > are somewhere along these lines: > > - If possible, the

Re: Reflexions around timers in the logs

Hi, first of all, it's great that this is being tackled. Thanks a lot! I don't have a very strong opinion on most of the details, but my thoughts are somewhere along these lines: - If possible, the most detailed information should be made available, not neccessarily by default, but at least

Re: [PATCH]: MINOR: small memory leak fixes

Hi David, thank you! I've done a minor edit below : On Mon, Aug 22, 2016 at 11:38:02PM +0100, David CARLIER wrote: > @@ -6858,6 +6860,10 @@ cfg_parse_users(const char *file, int linenum, char > **args, int kwm) > Alert("parsing [%s:%d]: '%s' only supports >

Re: Reflexions around timers in the logs

On Tue, Aug 23, 2016 at 11:34:39AM +0200, Willy Tarreau wrote: > Maybe something between all of this could consist in this : > > - we create a new date field (eg: %tr) to note the date the request > starts to arrive (end of the idle period) > - we use a new field for the request-only time

unsubscribe

unsubscribe

Re: Configure Log in Haproxy ( Need help )

Hi Qing, On 16-08-23 00:02:17, Qing Wang wrote: > And the haproxy.conf in /etc/rsyslog.d/ is: > # Create an additional socket in haproxy's chroot in order to allow > logging via > # /dev/log to chroot'ed HAProxy processes > #$AddUnixListenSocket /var/lib/haproxy/dev/log Uncomment this ^^^