fix(profiles): Enforce profile quotas on metrics buckets #2212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #2163 we decided not to enforce rate limits on processed profiles with
limit > 0
, to prevent complexity (see PR description).I wrongly assumed that quotas (i.e. rate limits with
limit:0
) would be correctly enforced by dropping the profile envelope item before metrics are extracted. I overlooked the fact that PoP Relays (where metrics are extracted) do not receive quota configuration, because they do not request it:relay/relay-server/src/actors/project_upstream.rs
Line 273 in 0505c88
Note that this only affects rate limits that are issued only for profiles. Rate limits issued for transactions correctly drop the processed profiles.
This PR fixes the issue by stripping the
has_profile
tag off metrics buckets if aProfile
rate limit is active.Fixes #2207
#skip-changelog