# Log rate limits violations without enforcing them

**URL:** <https://www.ruby-forum.com/t/log-rate-limits-violations-without-enforcing-them/243869>\
**Category:** NGINX\
**Created:** [January 20, 2016, 11:59am UTC](https://www.ruby-forum.com/t/log-rate-limits-violations-without-enforcing-them/243869 "2016-01-20T11:59:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [January 20, 2016, 11:59am UTC](https://www.ruby-forum.com/t/log-rate-limits-violations-without-enforcing-them/243869/1 "2016-01-20T11:59:02Z")

</div>

Hi list,

Before applying new rate limit values, I would like to check if these  
rules will have an impact on legitimate clients.

Is there a way to either set these rules in a “log only” mode, or a  
tool to analyse existing logs and see if the rule would have been  
triggered ?

Thanks,  
Adrien