Hi guys,
The haproxy-stats.pl check fails - rather often - on low-traffic backends like this:
Check haproxy CRITICAL - kki-prod-engagement-service:BACKEND sessions: 300.00%;
Because the stats looks like this:
stats: kki-prod-engagement-service-BACKEND=3;0;0;0;1
ie. it has 3 connections - and limit on "backend" is set to 1.

Thing is - the "limit" no. under 'backend' specificly is actually a dynamicly calculated limit - which is NOT enforced, unless minconn is set PER backend server and fullconn is set. see http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4-fullconn
I see no way of seeing from the stats page if fullconn is set - which means you can't automaticly figure out if the limit is at all relevant.

I COULD - make it ignore "low numbers".. like limits below 500 or something..
or add an option for giving a "list of backend names that have dynamic limits enabled" - and then only enable $slim (the name used in the script) checking on those ?

According to Nagios Docs, performance data items must be separated by whitespace. Currently the check_haproxy_stats.pl plugin uses a semicolon, which is wrong:

$perfdata .= sprintf "%s-%s=%u;%u;%u;0;%u;", $data[$pxname], $data[$svname], $data[$scur], $swarn * $data[$slim] / 100, $scrit * $data[$slim] / 100, $data[$slim];

...because of a new header in the response: 'name\tmessages'

A probable solution is described here: georgeyord@f10e2bb

hi, got this error in /var/log/graphite/console.log:

03/08/2019 23:55:24 :: Error parsing metric icinga2.lb1.services.haproxy_webfarm.haproxy-stats.perfdata.webfarm-www1=0;52428;58982;0;65536;webfarm-www2=0;52428;58982;0;65536;webfarm-www3=0;52428;58982;0;65536;webfarm-www4=0;52428;58982;0;65536;webfarm-BACKEND.max: Cannot parse path icinga2.lb1.services.haproxy_webfarm.haproxy-stats.perfdata.webfarm-www1=0;52428;58982;0;65536;webfarm-www2=0;52428;58982;0;65536;webfarm-www3=0;52428;58982;0;65536;webfarm-www4=0;52428;58982;0;65536;webfarm-BACKEND.max, invalid segment 52428

graphite expects the perfdata to be separated by spaces, like this: (just one proxy here):
Check haproxy CRITICAL - server: webfarm:www3 is MAINT; |webfarm-www1=3;52428;58982;0;65536; webfarm-www2=2;52428;58982;0;65536; webfarm-www3=0;52428;58982;0;65536; webfarm-www4=5;52428;58982;0;65536; webfarm-BACKEND=10;800;900;0;1000;

Thanks,
Gerardo