Skip to content

Name scalar based on percentile to report #478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

boomanaiden154
Copy link
Collaborator

Before this patch, the scalar name would end up as containing the value of the percentile rather than the percentile that we are trying to compute. We then end up with a bunch of one point metrics which clutters the UI and also means we cannot get any information about the actual percentiles. This patch fixes that by actually naming the scalar after the percentile that we are trying to compute.

Before this patch, the scalar name would end up as containing the value
of the percentile rather than the percentile that we are trying to
compute. We then end up with a bunch of one point metrics which clutters
the UI and also means we cannot get any information about the actual
percentiles. This patch fixes that by actually naming the scalar after
the percentile that we are trying to compute.
@boomanaiden154 boomanaiden154 requested a review from mtrofin March 31, 2025 04:25
@boomanaiden154 boomanaiden154 merged commit d3c3e86 into google:main Mar 31, 2025
13 checks passed
@boomanaiden154 boomanaiden154 deleted the fix-percentile-value branch March 31, 2025 04:31
svkeerthy pushed a commit that referenced this pull request Apr 10, 2025
Before this patch, the scalar name would end up as containing the value
of the percentile rather than the percentile that we are trying to
compute. We then end up with a bunch of one point metrics which clutters
the UI and also means we cannot get any information about the actual
percentiles. This patch fixes that by actually naming the scalar after
the percentile that we are trying to compute.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants