QS_EventKBytesPerSecLimit not respecting log-only mode?

[Simon Studer]

There seems to be a problem with the QS_EventKBytesPerSecLimit directive when QS_LogOnly is set to "on". The restrictions are applied even in log-only mode.

Is that the intended behaviour or should QS_EventKBytesPerSecLimit also be disabled in og-only mode?

We were able to isolate the behaviour with the following configurations:

QS_LogOnly                on
SetEnvIf Request_URI ".*" condition=1
QS_EventKBytesPerSecLimit condition 1

In this case the connection is limited.

[Pascal Buchbinder]

Yes, the "PerSec" rules are not affected by this log-only mode.

Reason: the throughput control rules use a closed loop system to control the bandwidth / events per second. A log-only mode would open the loop.

http://mod-qos.sourceforge.net/glossary.html#throughput

[Pascal Buchbinder]

Checked the code: interestingly, the log-only mode also affects the throttling rules (don't really understand why I this this as it really does not make much sense).
Also saw that some events are not set in this log-only mode - going to change this.
I'm also checking the "QS_EventKBytesPerSecLimit" rule again to see if the delay is skipped or not.

[Simon Studer]

This has caused us quite some headaches.

I could not find any documentation of this behaviour, is there a list of directives that are not disabled by the log-only mode?

[Pascal Buchbinder]

Ah see. Under such circumstances it would probably be better to deactivate everything (even a "simulation" does not make sense for all functions). Going to check if this is possible and update the documentation.