Settings - Spend allocation root allocation breaks when customers re-provision with different quota agreements

[Angelodaniel]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Customer URL in Jira issue

1. Currently customer X has for example 500M errors and setup allocation on that number
2. if customer X renews but increases the errors to 550M, the Root allocation total counts break and the calculation is off.

Expected Result

Numbers to be calculated effectively

Actual Result

Errors

Performance

Product Area

Settings - Spend Allocation

Link

See Jira Issue

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry]

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

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[Angelodaniel]

I recall that I could resolve this by "disabling the spend allocation"
And re-setting it again, but this is a big effort especially at "scale" so it should not happen in the first place

[keradus]

very important topic 👍🏻

Be careful - disabled spend allocation, each sentry project can burn whole quota of whole contract, as no spend allocation is configured

Also, if someone wanted to give 5M quota to project A, and 10M to project B, while whole contract states for 15M - after quota were disabled, the spend allocation is no longer aware which project used how much quota and Sentry is not allowing to configure A=5M, B=10M as 15M totals are no longer available for configuration - only quota allowed to configure is one that was not yet used given billing cycle.

[brianthi]

Thanks for raising up this issue and concerns. I'm backlogging the issue for now and will share this feedback with our PM team for prioritization. If we pick this up, will provide an update in the issue.

[Angelodaniel]

Hey @brianthi a month has gone by and the root allocation of the org is still broken. Can you revisit this as it will be a recurring problem each month until we have a fix for it in place.

Customers can potentially disable spend allocations and re-enable them directly after to "Reset" the numbers but at scale this becomes a big initiative which takes time and effort for the customer.

[keradus]

Customers can potentially disable spend allocations and re-enable them directly after to "Reset" the numbers but at scale this becomes a big initiative which takes time and effort for the customer.

as a customer, I need to avoid that.
Disabling root allocation and re-enabling it later means that I lost the so-far "consumed" counter per project in spend-allocation.
Imagine - I want to configure 2M events for project X, they used 0.5M. What I see in spend-allocation is that 0.5M was used already. Then, when I "Reset" the root spend-allocation and re-enable it, I see that... 0M was used in project's spend allocation. So I need to manually check it was 0.5 and set 1.5 for remaining billing month period.

Then I have ~100 projects, solution does not scale

[brianthi]

Hi, unfortunately I don't have an update to share right now. We are very aware of the problems that this bug causes and are prioritizing it accordingly with the planned work and technical debt we have. We will update this ticket once we have a meaningful update to share.