RE: 'clear table table' clearing only bottom entry? (1.5dev7)
Good morning Willy, I hope the new year is treating you well! I was wondering whether you were able to reproduce this issue? I had a quick look on git but couldn't immediately find any commits. If not, is there any further information or work I could do to assist? Unfortunately I'm not quite au fait with C! Thanks, Joe -Original Message- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: 28 November 2011 20:25 To: Price Joe JPC Cc: haproxy@formilux.org Subject: Re: 'clear table table' clearing only bottom entry? (1.5dev7) *SNIP* Using 'clear table backend1' on the socket seems to only be clearing the bottom entry of 'show table backend1' wheras the docs say In the case where no options arguments are given all entries will be removed. I'm reasonably sure this worked fine in 1.4. You might have caught a bug. I'll check this ASAP, this behaviour is not expected at all. *SNIP* Thanks, Willy
Re: 'clear table table' clearing only bottom entry? (1.5dev7)
Hi Joe, On Mon, Jan 09, 2012 at 09:47:05AM -, joe.pr...@vaisala.com wrote: Good morning Willy, I hope the new year is treating you well! I was wondering whether you were able to reproduce this issue? I had a quick look on git but couldn't immediately find any commits. No, I completely forgot about it. I think I should setup some bugtracking tool somewhere, because it's not the first time I forget about a bug when I can't work on it for a full week. If not, is there any further information or work I could do to assist? Unfortunately I'm not quite au fait with C! I just have to recheck the whole thread to see how to reproduce the issue. Thanks, Willy
Parsing Logs
Hi Everyone, I was wondering if anyone has a way to parse the logs and present them in a friendly format? Such as with AWStats or another log parser. Thanks Joe
Re: Parsing Logs
Hi Joe, On 2012-01-09 14:25, Joseph Hardeman wrote: I was wondering if anyone has a way to parse the logs and present them in a friendly format? Such as with AWStats or another log parser. There is Logstash [1] which includes patterns for parsing the HAProxy HTTP log format. It can either store the logs itself in elasticsearch has a reporting UI itself or can ship your logs anywhere you like. A popular (and really awesome) choice is Graylog [2] which provides all kinds or reporting and analytics on your logs. If you want to use your existing log analyzing stack and don't need the added information from the HTTP logs, you can use option httplog clf which generates Logs in the Common Log Format (clf) which is also used by default by Apache. It is more compatible with inflexible log parsers but gives you less information about requests than the default HTTP log does. [1] http://logstash.net/ [2] http://graylog2.org/ --Holger
