Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1261890 - Metrics are not properly updated/refreshed in JON UI
Metrics are not properly updated/refreshed in JON UI
Status: CLOSED ERRATA
Product: JBoss Operations Network
Classification: JBoss
Component: UI (Show other bugs)
JON 3.3.3
Unspecified Unspecified
medium Severity medium
: ER01
: JON 3.3.6
Assigned To: Ruben Vargas Palma
vsorokin
: Triaged
Depends On: 1261895
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-10 08:00 EDT by bkramer
Modified: 2016-10-31 21:42 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 11:30:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1519 normal SHIPPED_LIVE Critical: Red Hat JBoss Operations Network 3.3.6 update 2016-08-25 20:44:36 EDT

  None (edit)
Description bkramer 2015-09-10 08:00:17 EDT
Description of problem:
Metric values in Resource:Measurements and Group:Metrics portlets are not properly refreshed.

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

How reproducible:
Always

Steps to Reproduce:
1. Install JON 3.3.3 + EAP Plugins;
2. Navigate to JON UI -> Administration -> Metric Collection Templates -> JBossAS7 Standalone Server -> edit metric collection to set "Maximum Request Time" metric to 30 seconds;
3. Open two sessions of JON UI in the browser;
4. In the first one navigate to AutoGroup - JBossAS7 Standalone Servers -> Summary -> Activity and observe "Maximum Request Time" metric value;
5. In the second window navigate to the same AutoGroup - JBossAS7 Standalone Servers -> click on "Maximum Request Time" name/link -> click on 4h -> click on 1 h -> close this window;
6. Observe the value for "Maximum Request Time" - most likely it's changed;
7. Go back to the first window and confirm that initial value is not changed.
8. Press little refresh button in the right corner of the portlet and confirm that the value is not changed;
9. Request browser refresh -> confirm that metric value is changed.

Actual results:
Metric values are not refreshed in timely manner;

Expected results:
Metric values are regularly refreshed/updated;

Additional info:
Comment 2 Ruben Vargas Palma 2016-05-31 18:35:15 EDT
commit 9731418edd70d89ad411cf61412cf4fb1f7b5c56
Author: Ruben Vargas <rvargasp@redhat.com>
Date:   Wed May 11 12:38:54 2016 -0500

    Bug 1261890 - Metrics are not properly updated/refreshed in JON UI
Comment 4 Simeon Pinder 2016-07-07 04:23:04 EDT
Moving to ON_QA as available to test with the following build:
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=502442

Note: 	jon-server-patch-3.3.0.GA.zip maps to JON 3.3.6(jon-server-3.3.0.GA-update-06.zip)
Comment 5 vsorokin 2016-07-12 12:46:47 EDT
Executed required reproductive steps.

Observed as expected: metric values are updated in timely manner.
Comment 7 errata-xmlrpc 2016-07-27 11:30:49 EDT
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

Note You need to log in before you can comment on or make changes to this bug.