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

metricbeat/module/rabbitmq/queue: Fix data type for consumers.utilisation.pct #38436

Merged

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Mar 19, 2024

Proposed commit message

Fix mapping type for rabbitmq.queue.consumers.utilisation.pct to be scaled_float instead of long 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

  • 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

Logs

    queue_test.go:58: 
        	Error Trace:	C:/Users/jenkins/workspace/PR-38346-3-4409e966-4007-43a3-9905-b28d677060d2/src/github.com/elastic/beats/metricbeat/module/rabbitmq/queue/queue_test.go:58
        	Error:      	Not equal: 
        	            	expected: float64(0.7)
        	            	actual  : int64(0)
        	Test:       	TestFetchEventContents
--- FAIL: TestFetchEventContents (0.01s)

…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).
@andrewkroh andrewkroh added bug Metricbeat Metricbeat Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team labels Mar 19, 2024
@andrewkroh andrewkroh requested a review from a team as a code owner March 19, 2024 18:29
@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 Mar 19, 2024
Copy link
Contributor

mergify bot commented Mar 19, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @andrewkroh? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 19, 2024

💚 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 preview

Expand to view the summary

Build stats

  • Start Time: 2024-03-20T01:54:36.192+0000

  • Duration: 183 min 36 sec

Test stats 🧪

Test Results
Failed 0
Passed 28619
Skipped 1906
Total 30525

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@shmsr shmsr changed the title metricbeat/module/rabbitmq/queue - Fix data type for consumers.utilsation.pct metricbeat/module/rabbitmq/queue - Fix data type for consumers.utilisation.pct Mar 19, 2024
Copy link
Member

@shmsr shmsr left a 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.

CHANGELOG.next.asciidoc Outdated Show resolved Hide resolved
@shmsr shmsr changed the title metricbeat/module/rabbitmq/queue - Fix data type for consumers.utilisation.pct metricbeat/module/rabbitmq/queue: Fix data type for consumers.utilisation.pct Mar 19, 2024
@andrewkroh andrewkroh requested a review from a team as a code owner March 20, 2024 01:37
@andrewkroh andrewkroh force-pushed the bugfix/mb/rabbitmq-utilisation-pct branch from 8c82f16 to 8df4146 Compare March 20, 2024 01:54
@elasticmachine

This comment was marked as outdated.

@elasticmachine

This comment was marked as outdated.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @andrewkroh

@andrewkroh andrewkroh merged commit 5715699 into elastic:main Mar 20, 2024
138 of 142 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Metricbeat Metricbeat Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants