You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this moment when customers have setup spend allocation and they are re provisioned with a lower quota it will basically cause the spend allocations to be completely removed.
At scale if we remove this from the customer's org without them knowing it will have a huge impact on the visibility during the remainder of the month as it's also not possible to setup allocation on the quota but only on the available events which of course has been some the longer it goes unnoticed.
Solution Brainstorm
At this moment I think what would make most sense is to not remove it but recalculate the Old VS New quota and change all allocations with the same percentage change at the beginning of the cycle.
Notifying would be nice, but as the re provisioning happens on the Sentry side there is not a lot of notifying if you ask me.
Problem Statement
At this moment when customers have setup spend allocation and they are re provisioned with a lower quota it will basically cause the spend allocations to be completely removed.
At scale if we remove this from the customer's org without them knowing it will have a huge impact on the visibility during the remainder of the month as it's also not possible to setup allocation on the quota but only on the available events which of course has been some the longer it goes unnoticed.
Solution Brainstorm
At this moment I think what would make most sense is to not remove it but recalculate the Old VS New quota and change all allocations with the same percentage change at the beginning of the cycle.
Notifying would be nice, but as the re provisioning happens on the Sentry side there is not a lot of notifying if you ask me.
Product Area
Settings - Spend Allocation
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: