# Icon deprecation warnings causing rate limiting issues

**URL:** <https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586>\
**Category:** Product Support\
**Created:** [March 25, 2020, 7:46pm UTC](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586 "2020-03-25T19:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [March 28, 2020, 5:16pm UTC](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586/7 "2020-03-28T17:16:15Z")

</div>

Ok, I found something. This is not the problem @DaveK was having though.

> [@pmusaraj](#):
>
> The icon deprecation warnings are rate-limited

They are indeed rate-limited, but Logster rate-limits them even further, at one per minute per IP, resulting in 429 errors when there are multiple deprecation warnings in a single page load.

This actually causes deprecation warnings to get lost, making the /logs less valuable as a tool to find all deprecations…

> a 1 minute rate limit to all JS error reporting per IP

[https://github.com/discourse/discourse/commit/8db38de9d7d47b8c931ae0cc409c5550e37653b7#](https://github.com/discourse/discourse/commit/8db38de9d7d47b8c931ae0cc409c5550e37653b7#)

---

_[View the full topic](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586)._