Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1218129

Summary: Calltime metrics sort does not work properly
Product: [JBoss] JBoss Operations Network Reporter: bkramer <bkramer>
Component: Monitoring - CallTimeAssignee: Ruben Vargas Palma <rvargasp>
Status: CLOSED ERRATA QA Contact: Sunil Kondkar <skondkar>
Severity: low Docs Contact:
Priority: medium    
Version: JON 3.3.0CC: fbrychta, rvargasp, skondkar, spinder, tsegismo
Target Milestone: DR01Keywords: Triaged
Target Release: JON 3.3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 15:29:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1218150    
Bug Blocks:    
Attachments:
Description Flags
screen shot that shows incorrectly sorted values; none

Description bkramer 2015-05-04 09:13:29 UTC
Created attachment 1021609 [details]
screen shot that shows incorrectly sorted values;

Description of problem:

In Calltime page, some values are displayed in ms and others in s. When using sort a column option, JON sorts the values as strings which gives a wrong result (see attached screen shot).

Version-Release number of selected component (if applicable):
JBoss ON 3.3.0, 3.3.1

How reproducible:
Always

Steps to Reproduce:

1. Configure Response time metrics or just simply navigate to RHQ Server -> Deployments -> rhq.ear -> Subdeployments -> coregui.war -> web -> Monitoring -> Schedules and enable "Response Time" metric.

2. For the same resource, navigate to Monitoring -> Calltime and wait for the collected data to be displayed;

3. Click on "Total Time" (make sure that there are metrics shown in s(seconds) and ms (miliseconds)) and then click on the arrow next to the "Total Time" column;

Actual results:
Values are sorted but as strings so the "Total Time" will show:
3.0 ms
3.5 s
4.0 ms
4.0 ms
4.5 s
5.0 ms
...

Expected results:
Values should be sorted properly:
3.0 ms
3.5 ms
4.0 ms
4.0 ms
5.0 ms
...
3.5 s
4.5 s
...


Additional info:
see attached screen shot - calltime_metrics.png.

Comment 4 Thomas Segismont 2016-03-16 08:40:43 UTC
Merged in master

commit 449d6b185d3ae24e7d0d11ed5612773a4610e5f2
Merge: 4ffe7c8 9c19651
Author: Thomas Segismont <tsegismont>
Date:   Wed Mar 16 09:39:42 2016 +0100

    Merge pull request #220 from rubenvp8510/Bug/1218129

Comment 5 Mike McCune 2016-03-28 23:30:47 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 Simeon Pinder 2016-06-18 01:11:56 UTC
Moving to ON_QA as available to test with JON 3.3.6 DR01 brew build:
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=499890

Comment 8 Sunil Kondkar 2016-06-28 09:43:36 UTC
Verified on version : 3.3.0.GA Update 06 Build Number :	675641d:2fcd5b7
Verified that Calltime metrics sort works as expected.

Comment 10 errata-xmlrpc 2016-07-27 15:29:58 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://rhn.redhat.com/errata/RHSA-2016-1519.html