Hi Dmitri,
On Tue, Aug 10, 2010 at 02:57:30PM -0700, Dmitri Smirnov wrote:
> Hi,
>
> i have been using haproxy for a couple of months and the product is very
> solid, thank you.
> It is now taking production traffic.
>
> The stats page is very useful with respect to rps and etc.
> In our case it would be helpful to add a average backend latency over a
> second/minute
> and or per individual b/e server.
That's something I've been considering now that I have new functions which
might help keeping such stats. However, I don't want to add *too much* stats
either because adding stats everywhere starts to inflate the code and to
slow it down. But I agree that the average connect time, response times
and error rates would greatly help.
> I know haproxy logs per request latencies but parsing logs at these rates is
> not fun.
you have "halog" in the contrib directory. It can process around one gigabyte
of logs per second and report you exactly what you're looking for ;-) Try it
with :
$ halog -srv < logfile
It will report fields per server. Using it with "-st" instead reports a more
global status report.
> For our product haproxy represents the actual endpoint and just looking at
> the stats it would be really helpful to see what the latency per server or
> even the whole backend which then can be plotted.
Well, added to the 1.5 roadmap now ;-)
Cheers,
Willy
