fix(tracemetrics): Switch experimental backend to kwarg rate #101520
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on some digging, last time we tried to use an option with metrics it caused INC-1101 and INC-1130 with spikes hitting db in production as some metrics are module/import level. This will be slower (as it needs a deploy to change volume) but we can still kill switch via tracemetrics-ingestion in relay.
AbhiPrasad
approved these changes
Oct 15, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Based on some digging, last time we tried to use an option with metrics it caused INC-1101 and INC-1130 with spikes hitting db in production as some metrics are module/import level. This will be slower (as it needs a deploy to change volume) but we can still kill switch via tracemetrics-ingestion in relay.