You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tested with Metricbeat 7.2.0 BC2, Elasticsearch 7.2.0 BC2 and Kibana 7.2.0 BC2.
I think this bug is introduced by #12089. When testing metricbeat rabbitmq module with 7.2.0 BC2, I cannot see any rabbitmq.queue.consumers.utilisation.pct data points from the metrics. For example, from Kibana I can see rabbitmq.queue metric:
Tested with Metricbeat 7.2.0 BC2, Elasticsearch 7.2.0 BC2 and Kibana 7.2.0 BC2.
I think this bug is introduced by #12089. When testing metricbeat rabbitmq module with 7.2.0 BC2, I cannot see any
rabbitmq.queue.consumers.utilisation.pct
data points from the metrics. For example, from Kibana I can seerabbitmq.queue
metric:But querying directly from rabbitmq shows:
Based on
rabbitmqctl
result, rabbitmq.queue.consumers.utilisation.pct should be 1.0 instead.I removed the `` from the code and rebuilt/ran metricbeat:
After that
consumer_utilisation
data showed up:The text was updated successfully, but these errors were encountered: