fix: Fix query tracking tags (== is faulty), set previous bucket sizes (DEV-3776) #3305
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.
Pull Request Checklist
Checked that the labels are now differentiated locally. The problem was == is really lax and just compares the object ids (or something). Cats'
===
would work, but then anEq
has to be derived and imported. The problem was.timeout
wasn't added, so it was compared against an entirely different set of objects.Second, now that the Grafana dashboard calculates the heatmaps correctly and bucket differences are pristine, I'm restoring the wide bucket range.
Task Description/Number
Issue Number: DEV-
PR Type
Basic requirements for bug fixes and features
Does this PR introduce a breaking change?