Replies: 6 comments
|
I will have a look into it. 👍 |
0 replies
0 replies
|
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" |
0 replies
|
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 |
0 replies
|
Closing this issue. If this check warns about sessions, this is a HAProxy configuration issue. Unsetting or setting |
0 replies
|
This is the haproxy.conf related to my screenshot above (relevant parts only): |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
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" ?
All reactions