Bug 1007413
Summary: | Metric maximum/minimum value | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Libor Fuka <lfuka> |
Component: | Monitoring -- Other | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | JON 3.2 | CC: | lfuka, myarboro |
Target Milestone: | ER01 | ||
Target Release: | JON 3.2.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-02 20:34:33 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: |
Description
Libor Fuka
2013-09-12 12:48:26 UTC
I refresh about every 5-10 sec. If its designed i think its not good. The same functionality in JON 3.1.2 shows Minimum/Maximum and Last Value immediately after setting new collection time. Its fixed in JON 3.2.0.ER1 server |