fix(spans): Fixes span outcomes and inherited rate limits #3793
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.
Span outcomes are currently off when created from rate limited transactions in the
transaction_indexed
category. All of the dropped outcomes are also added to the accepted, because the metrics are not dropped.Additionally outcomes for the span category were emitted when there was a limit for
transaction_indexed
instead of just emitting them fromspan_indexed
.Implementation notes:
Need to drop the metrics based on the enforcement instead of the rate limits, because it is correct that there are no rate limits added for the inherited category. We wouldn't want to start dropping standalone spans because of a transaction quota.