Logging only mode and %{mod_qos_cr}e %{mod_qos_ev}e %{mod_qos_con}e values in access logs

[sophie]

Hi,
I have this running in detction mode only / logging mode, and put this LogFormat in.

I would like to see values of %{mod_qos_cr}e %{mod_qos_ev}e in my access log, but I don't. Their values contains hypens.

How should I enable logging of these values. I see similar in their error logs. Likely because the rules are not currently enforced, are they?

LogFormat "%h %l %u %t \"%r\" %>s %b %I %O \"%{Referer}i\" \"%{User-agent}i\" %D \"%{Authorization}i\" %{remote}p:%{Host}i:%p %{mod_qos_cr}e %{mod_qos_ev}e %{mod_qos_con}e %{QS_SrvConn}e %{QS_AllConn}e id=%{UNIQUE_ID}e %{QS_ConnectionId}e %{mod_qos_user_id}e %{QS_Country}e #%P" devops

Kind regards, Sophie.

[Pascal Buchbinder]

Well, you need to configure some QS_* directives in order to get any values of these counters.

[sophie]

Hi Pascal,

I did configure:
SetEnvIfPlus Request_URI ^/fleet-service/Tracking.*$ QS_Limit
QS_ClientEventLimitCount 100 1
QS_ErrorResponseCode 509
<Location/>
ResponseSetEnvIfPlus QS_ErrorNotes 067 RATELIMITED=1
ResponseHeaderPlus set Retry-After 1 env=RATELIMITED
</Location>

Please let me know directives I missed, would you?

Thanks, Sophie

[Pascal Buchbinder]

you may use the

   %{QS_Limit_Counter}e %{QS_Limit_Remaining}e

variables to track the clients QS_Limit counter.

[Rakesh]

i used this directives "mod_qos_cr" in my apache access log. value is getting in the log. but i am confused , weather its value of QS_LocRequestLimitMatch or QS_LocRequestPerSecLimitMatch?

[Pascal Buchbinder]

Of course, the pattern is relevant on how many requests match them (which resource is accessed).

[Rakesh]

yes... but i am confused because the QS_LocRequestLimitMatch and QS_LocRequestPerSecLimitMatch are different. so the value getting from mod_qos_cr is what basis?

[Pascal Buchbinder]

The mod_qos_cr variable shows the number of concurrent HTTP requests for with the rule applies.

Example: if you have configured

QS_LocRequestLimitMatch       ^/index.html$  10
QS_LocRequestPerSecLimitMatch ^/index.html$ 200

and your server is currently processing three requests to /index.html and two to /image.png, the value of the mod_qos_cr is "3" for the requests to /index.html because three requests matches the pattern of the rule applied to the request and "0" for the requests to /image.png (no rule match).