Bug 1461800 - Metrics numeric value for records with only one value are reported as array and not a number
Summary: Metrics numeric value for records with only one value are reported as array a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rubygem-fluent-plugin-collectd-nest
Version: 4.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.1.3
: ---
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: oVirt-Metrics-and-Logs 1455608
TreeView+ depends on / blocked
 
Reported: 2017-06-15 11:03 UTC by Shirly Radco
Modified: 2017-07-06 07:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-06 07:31:33 UTC
oVirt Team: Metrics
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ViaQ fluent-plugin-collectd-nest pull 7 0 None None None 2017-06-15 11:08:28 UTC
Red Hat Product Errata RHEA-2017:1693 0 normal SHIPPED_LIVE rubygem-fluent-plugin-collectd-nest bug fix and enhancement update 2017-07-06 11:24:42 UTC

Description Shirly Radco 2017-06-15 11:03:56 UTC 
Description of problem:
Metrics numeric value for records with only one value are reported as array and not as a number.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Set up metrics store.
2. Set up metrics on the hosts and engine.
3. Search for the value of plugin such as cpu, memory and see that is reported as a number.

Actual results:
field is reported as an array.

Expected results:
field is reported as a number.

Additional info:
Comment 2 Sandro Bonazzola 2017-06-15 15:22:19 UTC 
Need a rebase on 0.1.4
Comment 4 Lukas Svaty 2017-06-20 10:03:27 UTC 
tested on memory and cpu, both values reported as numbers

ovirt-engine-metrics-1.0.4.2-1.el7ev.noarch
Comment 6 errata-xmlrpc 2017-07-06 07:31:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1693
Note You need to log in before you can comment on or make changes to this bug.