getsentry / getsentry/sentry

Separate Rate Limits for Transactions and Errors

Open
#79,880 12 comments 1 reaction 0 assignees View on GitHub
Feature Product Area: Ingestion and Filtering
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

**Separate Rate Limits for Transactions and Errors**

We would like the ability to set distinct rate limits for transactions and errors. Our goal is to allow errors to flow seamlessly, while imposing stricter rate limits on transactions. Currently, rate limits are applied per DSN, which limits flexibility. Although we recognize that a sampling rate for transactions exists, it is not always feasible to adjust it through code, especially in cases where a complex rollout process is required. Therefore, our request is for a feature that enables separate rate limits specifically for transactions and errors.

### Solution Brainstorm

_No response_

### Product Area

Settings - Projects

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.