Skip to content
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

Merged
merged 2 commits into from
Feb 25, 2021

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Feb 24, 2021

What does this PR do?

  • Store cloudfoundry.container.cpu.pct in decimal form.
  • Store it as a scaled_float.
  • Remove existing helper for common code that doesn't make so sense to reuse now.

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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

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.
@jsoriano jsoriano added review Metricbeat Metricbeat needs_backport PR is waiting to be backported to other branches. Team:Integrations Label for the Integrations team breaking change labels Feb 24, 2021
@jsoriano jsoriano self-assigned this Feb 24, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Feb 24, 2021
@botelastic
Copy link

botelastic bot commented Feb 24, 2021

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 24, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #24219 updated

  • Start Time: 2021-02-24T18:45:54.894+0000

  • Duration: 47 min 25 sec

  • Commit: 110fc3f

Test stats 🧪

Test Results
Failed 0
Passed 9141
Skipped 2247
Total 11388

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 9141
Skipped 2247
Total 11388

Copy link
Contributor

@ycombinator ycombinator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Copy link
Contributor

@kaiyan-sheng kaiyan-sheng left a 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!

@jsoriano jsoriano merged commit 2cf650c into elastic:master Feb 25, 2021
@jsoriano jsoriano deleted the cloudfoundry-container-cpu-percent branch February 25, 2021 10:46
@jsoriano jsoriano added v7.13.0 and removed needs_backport PR is waiting to be backported to other branches. labels Feb 25, 2021
jsoriano added a commit to jsoriano/beats that referenced this pull request Feb 25, 2021
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)
jsoriano added a commit that referenced this pull request Mar 1, 2021
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants