Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/sentry/locale/en/LC_MESSAGES/django.po
Original file line number Diff line number Diff line change
Expand Up @@ -1953,7 +1953,7 @@ msgstr ""
msgid ""
"Rate limits apply on a per-minute basis, which means that they rollover at "
"the start of a new minute. When you attempt to send an event and the project "
"is over it's quota, the client will receive an HTTP 429 (Too Many Requests) "
"is over its quota, the client will receive an HTTP 429 (Too Many Requests) "
"response."
msgstr ""

Expand Down
2 changes: 1 addition & 1 deletion src/sentry/templates/sentry/projects/quotas.html
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ <h2>{% trans "Rate Limits" %}</h2>
<form action="" method="post" class="form-stacked">
<p>{% blocktrans %}With the nature of Sentry, sometimes the amount of data collected can be overwhelming. You can set rate limits per-project to ensure that a single flood of errors won't affect any other projects utilizing Sentry.{% endblocktrans %}</p>

<p>{% blocktrans %}Rate limits apply on a per-minute basis, which means that they rollover at the start of a new minute. When you attempt to send an event and the project is over it's quota, the client will receive an HTTP 429 (Too Many Requests) response.{% endblocktrans %}</p>
<p>{% blocktrans %}Rate limits apply on a per-minute basis, which means that they rollover at the start of a new minute. When you attempt to send an event and the project is over its quota, the client will receive an HTTP 429 (Too Many Requests) response.{% endblocktrans %}</p>

{% if not has_quotas %}
<p><strong>{% blocktrans %}Note: The Sentry application is not configured to manage rate limits.{% endblocktrans %}</strong></p>
Expand Down