Response time from HAproxy stats about haproxy_exporter HOT 9 CLOSED

And "it's not 100% correct but at least allows you to know what's there" is perfectly fine for an operational monitoring system – we don't promise exactness anywhere. There are plenty of cases with a steady enough request stream that these numbers are at least indicative.

from haproxy_exporter.

Tossing our hat in here that we would like this, even though it's not perfect.

from haproxy_exporter.

Why don't cut a version with this as a gauge? Even though the numbers are not 100% reliable it is better than nothing, awaiting a better counter from HAProxy.
Perhaps a flag to include these values by choice would be an ok solution?

from haproxy_exporter.

The problem is that we need a counter to do it properly, and that's not a counter. From when I looked into this about a year ago it's an exponentially decaying average, and depending on your request rate may be quite off the true value. What we really need to do is add counters for latency to haproxy.

from haproxy_exporter.

Sorry I didn't look into that @brian-brazil. In my case that number is better than nothing right now, but is nice to know it doesn't necessarily represents the real value.

from haproxy_exporter.

I have been exporting response time (more specifically, as histogram on the Tr timer in the HAProxy HTTP log) from the HAProxy logs with this exporter http://git.cbaines.net/prometheus-haproxy-log-exporter/ (which I wrote for this purpose).

I'm not sure the stats page is fit for this purpose, but exporting data from the logs works very well.

from haproxy_exporter.

Thankz @cbaines - looks interesting. I will definitely havce a look.

from haproxy_exporter.

I want to throw my vote in that we include this in a release. I understand it may not be perfect, but we currently use these metrics in various graphs and operators will miss them if we migrated to this exporter. Maybe we only enable them with a flag?

from haproxy_exporter.

I'm in favour of including the times that are there, even if gated behind a flag and/or equipped with a big warning. That the ideal form of the data is not available does not mean we should ignore the information that is there out of spite.

from haproxy_exporter.