mod_qos works as expected, but status on /qos doesn't change

[Jay Sullivan]

Here's my test config:

LoadModule qos_module modules/mod_qos.so
QS_EventCount on
SetEnvIf Request_URI        ^(?!/qos).*$ LimitLogin
QS_ClientEventLimitCount    5 60 LimitLogin

My test client is blocked as expected after 5 connection attemps and I see "access denied" show up in the apache logs. But the status page at /qos or /qos/console?action=search&address=* doesn't show any indication that anything is blocked. I see lowprio go from no to yes (and it never returns to no) but that's it. I do see mod_qos(067) increment at /qos?auto. This is what I see from the /qos/console page while that client IP is blocked:

192.168.1.42 vip=no lowprio=yes block=0/0 limit=0/0

Should I expect to see numbers next to block or limit change when a client IP is has triggered QS_ClientEventLimitCount? I'm using mod_qos-11.70-1.el7.x86_64 on RHEL7.

Thanks!
~jps

[Jay Sullivan]

I think I figured it out via harder RTFMing:
"Only the default rule (QS_Limit) is accessibly by the status viewer (you may use the console to view other variables alternatively)."

[Pascal Buchbinder]

Hi jps
Thank you for sharing your experience using mod_qos with us.