Skip to content

fix: replace typo in RateLimits section #6113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 19, 2023
Merged
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
Original file line number Diff line number Diff line change
Expand Up @@ -261,7 +261,7 @@ A good way to set a project rate limit is by figuring out the expected event vol
1. In the "KEY USAGE IN THE LAST 30 DAYS" graph, look for the highest point, or the maximum daily rate. In the example below, the maximum daily rate in the last month is less than 34K:
![Calculating rate limits](manage-event-stream-14-new.png)
<!-- image notes: Sentry, airflow, Santry, app-frontend -->
1. Based on the rate, choose a **daily** maximum value or ceiling. In this example, we calculated a daily maximum of approximantely 35K, which is around 1458 events an **hour**, or about 24 events a **minute**.
1. Based on the rate, choose a **daily** maximum value or ceiling. In this example, we calculated a daily maximum of approximately 35K, which is around 1458 events an **hour**, or about 24 events a **minute**.
1. Set a daily, hourly, or minute-based rate limit. We recommend using a minute-based rate to avoid situations where a random event spike might exhaust your daily or hourly quota and leave you without event data for a long period.

You should periodically go back and check the graph to see the number of events dropped due to rate limiting and, if needed, revisit your settings.
Expand Down