-
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
metricbeat/module/rabbitmq/queue: Fix data type for consumers.utilisation.pct
#38436
metricbeat/module/rabbitmq/queue: Fix data type for consumers.utilisation.pct
#38436
Conversation
…ation.pct Fix mapping type for `rabbitmq.queue.consumers.utilisation.pct` to be `scaled_float` instead of `long` because the values range on `[0, 1.0]`. Previously, truncation converted the value to an integer so it either reported zero or one. There was a bug in the unit tests that did not catch this until we updated to testify 1.9.0 (stretchr/testify#1531).
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Temporary fix for elastic#38436.
consumers.utilisation.pct
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.
Left one comment. Otherwise, it looks good.
consumers.utilisation.pct
consumers.utilisation.pct
8c82f16
to
8df4146
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
💚 Build Succeeded
History
cc @andrewkroh |
Proposed commit message
Fix mapping type for
rabbitmq.queue.consumers.utilisation.pct
to bescaled_float
instead oflong
because the values range on[0.0, 1.0]
. Previously, truncation converted the value to an integer so it either reported zero or one.There was a bug in the unit tests that did not catch this until we updated to testify 1.9.0 (stretchr/testify#1531). This PR removes the temporary testify v1.8.4 pin.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Logs