-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Store cloudfoundry.container.cpu.pct in decimal form #24219
Store cloudfoundry.container.cpu.pct in decimal form #24219
Conversation
Percentages should be stored in decimal form, and can be stored as scaled floats. Some code is refactored to remove previous helper that makes less sense now.
Pinging @elastic/integrations (Team:Integrations) |
This pull request doesn't have a |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you for making the change!
Percentages should be stored in decimal form, and can be stored as scaled floats. Some code is refactored to remove previous helper that makes less sense now. (cherry picked from commit 2cf650c)
What does this PR do?
cloudfoundry.container.cpu.pct
in decimal form.scaled_float
.Change is breaking, but it doesn't affect to existing dashboards, and this module is in beta stage.
Why is it important?
It is preferred to store percentages in decimal form, and
scaled_float
is enough to store them.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues