Avoid Rate Limiting with Query Batching
This post is part of our debugging series, where we share tricky challenges and solutions while building Sentry. On March 4th, 2024, the most metal incident happened - INC-666 INC-666, in a nutshell, was where the issue alert rule post-processing step was flooded with more load than it could handle, and alerts that were supposed to have fired did not. This means that Sentry customers might not be receiving alerts if the query that would have triggered the alert is rate-limited.