You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's pretty obvious that this backend will never have any servers, therefore it should be possible to exempt such backends from monitoring. So far, up to release 1.1.1, this was possible by providing -O BE_http_no_match:x as a parameter.
With 1.2.0 running in debug mode I can see that the override is still processed correctly but the check goes critical and complains exactly about that backend which should rather be ignored.
In HAProxy I have a default backend which catches all cases where no ACL was matched in a frontend. It just looks like that
It's pretty obvious that this backend will never have any servers, therefore it should be possible to exempt such backends from monitoring. So far, up to release 1.1.1, this was possible by providing
-O BE_http_no_match:x
as a parameter.With 1.2.0 running in debug mode I can see that the override is still processed correctly but the check goes critical and complains exactly about that backend which should rather be ignored.
I'm not really a Perl guy, but the latest code change around the code comment "Merge the two arrays" looks a suspicious to me, because the rewritten regular expression https://github.com/DinoTools/monitoring-check_haproxy/blob/1.2.0/check_haproxy#L150-L154 doesn't match the
x
case anymore, https://github.com/DinoTools/monitoring-check_haproxy/blob/1.2.0/check_haproxy#L459, and the configuration doesn't get applied.The text was updated successfully, but these errors were encountered: