haproxy-status3: Non-sense check

[10RUPTiV]

Hi,

The data gathering some haproxy csv is having some part that need to be excluded from the check!

The SERVERNAME " BACKEND " will always be /1.0 , that mean it will always generate a CRITICAL.

We spoke with Haproxy team (we have a business contract with them) and they told us, there's no way in the config to increase the /1.0 on for this one.

Maybe it should be remove from the "check" ?

[markuslf]

I will have a look into it. 👍

[markuslf]

It seems that you are referring to the Sessions column, and you get a CRIT, because 2 out of 1 possible sessions are used (which is weird).

I had a look at the plugin output in one of our datacenters. There, the output looks like this:

So in BACKEND, our HAproxy supports up to 300 connections. In this special case, we are running HAProxy version 2.4.17, and check plugin version 2022021602. What do you use on your side?

[10RUPTiV]

Markus,

We are using HAproxy EE 2.4r1 and the latest plugin...

But in our backend config, we have not set any limit... that's probably why we have a limit of "1"

[10RUPTiV]

Just did a little test and I can confirm that having no maxconn in the backend setting, equal "unlimited" until we reach the GLOBAL maxconn

[markuslf]

Closing this issue. If this check warns about sessions, this is a HAProxy configuration issue. Unsetting or setting maxconn to appropriate values helps (as intended and expected).