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] consumer_utilisation issue with RabbitMQ module in 7.0.0 #11833

Closed
sygnowskip opened this issue Apr 16, 2019 · 4 comments
Closed
Assignees
Labels
bug Metricbeat Metricbeat module Team:Integrations Label for the Integrations team

Comments

@sygnowskip
Copy link

Hi,
after update of Metricbeat from version 6.6.2 to 7.0.0 module for RabbitMQ monitoring is not working.

I'm receiving following errors (multiple):
1 error: wrong format in "consumer_utilisation": expected integer, found <nil>;

Configuration for rabbitmq.yml:

- module: rabbitmq
  metricsets: ["queue"]
  enabled: true
  period: 180s
  hosts: ["localhost:15672"]
  fields.beattype: "rabbit"

I've verified it and RabbitMQ is returing consumer_utilisation as null, but version 6.6.2 is able to parse it correctly, but 7.0.0 is throwing an error.

Is it expected behavior? Should I change something in configuration?

@exekias exekias added Team:Integrations Label for the Integrations team bug module labels Apr 16, 2019
@jcoeltjen
Copy link

jcoeltjen commented Apr 17, 2019

Same issue here.
The used schema for the object received by from the RabbitMQ management API did not change.
https://github.com/elastic/beats/blob/v6.6.2/metricbeat/module/rabbitmq/queue/data.go

Maybe the implementation of schema
or one of the helpers in mapstriface did change.

Update

The plugin still works fine in 6.7.1 too.
Also there are no changes in schema.go and mapstriface.go from the 6.7 branch to master.
The issue must be located somewhere else.

@odacremolbap
Copy link
Contributor

@sygnowskip @jcoeltjen

I'm trying to reproduce the issue, no luck so far.
I guess the reason is that I'm not receiving the field, vs receiving it with no data.
Is that your case?

@odacremolbap
Copy link
Contributor

able to reproduce, dismiss my previous comment

@odacremolbap
Copy link
Contributor

@sygnowskip @jcoeltjen fix for this issue has been merged.
We expect it to be released 7.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Metricbeat Metricbeat module Team:Integrations Label for the Integrations team
Projects
None yet
Development

No branches or pull requests

7 participants