-
Notifications
You must be signed in to change notification settings - Fork 5k
fix(metricbeat): Accept Float values as float not long #47792
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
Open
ash-darin
wants to merge
9
commits into
elastic:main
Choose a base branch
from
ash-darin:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+8
−8
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
Make floats into floats
Accept floatingpoint values as float
Contributor
🤖 GitHub commentsJust comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Restore bytes designation
Changes values to double to more closely match origin filetype float64. botch double in elasticearch and float64 in GO are IEEE754 conforming 64bit floats.
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed commit message
Fix Docker values to take into account floating point numbers
Metricbeat outputs floats, as evident here: Link to source that produces these values, as these are not absolute values but values for a fraction of a time ("per_second").
But with the exception of the "dropped" values, these are treated as long and therefore simply truncated. To preserve the values to a certain degree, treat all incoming ("in") and outgoing ("out") values as floats, like "dropped".
In GO, float64 is a IEEE754 conforming 64bit floating point number.
in Elastricsearch double is a IEEE754 conforming 64bit floating point number.
Therefore mapping these values to double is the closest match to any possible values produced by metricbeat.
Checklist
Disruptive User Impact
This should not disrupt user experience.
Use cases
You can now evaluate the values with a higher degree of accuracy.