Hi list,
I am not entirely sure yet whether it's a bug or intended. If it is
intended, it might make sense to just add another option for it.
So like I said, it's about haproxy_frontend_http_responses_total via
PROMEX.
In this case, we have some weird values for our backends that we use for
baselining, rate-limits etc.
haproxy_frontend_http_responses_total counts any frontend/listen
request.
The problem is, it also counts requests to monitor-uri. Technically, I'd
say that's totally fine. Since those are not represented in the logs,
I'd have expected them to be not counted in PROMEX either. This might
already explain our weird values.
Would it make sense to add an option, to not count those? Or is it a bug
/ not intended and just needs to be fixed? I'd open a GitHub issue then
I guess.
Steps to reproduce:
Have a PROMEX endpoint, e.g. via
http-request use-service prometheus-exporter if { path,url_dec -m reg
^/+metrics$ }
Have a listener + monitor-uri, like:
monitor-uri /haproxy-check
monitor fail if { nbsrv() lt 1 }
Or using my generic test config (including unnecessary options):
https://gist.github.com/idl0r/28c7b823925978d715a51f888c8230b7
curl -s http://127.0.0.1:8201/metrics | grep
'haproxy_frontend_http_responses_total{proxy="listen_test"'
curl -s https://127.0.0.1:61630/haproxy-check
curl -s http://127.0.0.1:8201/metrics | grep
'haproxy_frontend_http_responses_total{proxy="listen_test"'
Any thoughts?
--
Regards,
Christian Ruppert
#gernePerDu / #CallMeByMyFirstName
