Settings - DSN should give the possibility to adjust/create a Transaction rate limit

[Angelodaniel]

Problem Statement

Currently we only have the rate limit for Errors but not for Performance. For mobile use cases with adoption rates or when redeploying is slow this causes a problem when quota runs out too quickly.

Also some companies don't have the capacity to adjust sample rates on the go.

Solution Brainstorm

No response

Product Area

Settings

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-settings-general for triage ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-performance for triage ⏲️

[gggritso]

@Angelodaniel thanks for raising this! I'm going to follow-up and find the right team to tackle this issue (maybe Performance, maybe not Performance)

[gggritso]

@Angelodaniel I talked to some folks and got a bit more info. If you're interested you can read through the thread and chime in, but the summary is that this is a big ask, and there aren't any plans to tackle this just yet. I'm going to re-assign this area to spike protection, since it feels the closest to me, and keep it open.

[getsantry[bot]]

Routing to @getsentry/product-owners-settings-spike-protection for triage ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-settings-projects for triage ⏲️

[keradus]

Very good one!

Right now, our team is having a contract with Sentry, and we pay for Errors and for Transactions (we already evaluate how to transition into Spans).

We have spend-limits for both, Errors and Transactions, and use it to distribute quota across few projects in single contract.

Now, I want to set-up rate-limiting for them. If some clients started sending extra data (even sampled to x% on client level!), if total of all client would create a huge load that would consume my monthly quota, I want to be able to prevent it by rate-limiting.

Right now, I'm able to do it for Errors, but not for Transactions. That means I pay for Transactions, but i cannot protect myself from any wrongly reported spikes in them.

Can we please add rate-limiting for all events we pay for? (Transactions, Spans, Replays, ...)

[yuseferi]

Very good one!

Right now, our team is having a contract with Sentry, and we pay for Errors and for Transactions (we already evaluate how to transition into Spans).

We have spend-limits for both, Errors and Transactions, and use it to distribute quota across few projects in single contract.

Now, I want to set-up rate-limiting for them. If some clients started sending extra data (even sampled to x% on client level!), if total of all client would create a huge load that would consume my monthly quota, I want to be able to prevent it by rate-limiting.

Right now, I'm able to do it for Errors, but not for Transactions. That means I pay for Transactions, but i cannot protect myself from any wrongly reported spikes in them.

Can we please add rate-limiting for all events we pay for? (Transactions, Spans, Replays, ...)

That sounds like a reasonable feature request 👍