Bug 1043382 - Availability is charted for incorrect custom interval
Summary: Availability is charted for incorrect custom interval
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.9
Hardware: All
OS: All
unspecified
unspecified vote
Target Milestone: ---
: RHQ 4.10
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 07:11 UTC by Ilya Maleev
Modified: 2014-10-13 11:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:30:09 UTC


Attachments (Terms of Use)
screenshot (113.92 KB, image/png)
2013-12-16 07:11 UTC, Ilya Maleev
no flags Details

Description Ilya Maleev 2013-12-16 07:11:22 UTC
Created attachment 837123 [details]
screenshot

Description of problem:
There is a possibility to configure a custom interval in Metrics tab.
It is applied to metrics sharts, but not completely applied to availability line. Availability chart interval has the same lenght as expected, but its end is always a current moment - as fact, it is "Last <custom interval length>".

How reproducible:
Always for me

Steps to Reproduce:
1. Open Monitoring-Metrics tab for any resource.
2. Click Custom button in the interval selection band and configure some interval in the past - its start and end should be before the current moment. Apply.

Expected results:
2. Selected interval has been applied to availability line and all available metrics charts.

Actual results:
2. Metrics charts are OK, but Availability is NOK.

See screenshot.
1 - selected interval is 7:09 - 7:12 (3 minutes length).
2 - metric shart is shown for expected interval
3 - availability line is shown for the last 3 minutes - the used interval has the same length as a configured one, but its end is a current moment.

Comment 1 Jay Shaughnessy 2014-01-08 22:28:39 UTC
My thought was that this had already been fixed a while back and my local test does not show the issue.  I'm setting to ON_QA for 4.10.

Comment 2 Heiko W. Rupp 2014-04-23 12:30:09 UTC
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.


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