Bug 1114200

Summary:	Data from late measurement reports should get aggregated
Product:	[JBoss] JBoss Operations Network	Reporter:	John Sanda <jsanda>
Component:	Core Server, Storage Node	Assignee:	John Sanda <jsanda>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Armine Hovsepyan <ahovsepy>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	ahovsepy, hrupp, loleary, mfoley
Target Milestone:	ER04
Target Release:	JON 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1114199	Environment:
Last Closed:	2014-12-11 14:01:44 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:	1114199
Bug Blocks:	1133609

Description John Sanda 2014-06-28 15:06:36 UTC

+++ This bug was initially created as a clone of Bug #1114199 +++

Description of problem:
First I need to define a "late measurement report". The easiest way is with an example. Suppose the current time is 15:00. The data purge job runs and data from 14:00 to 15:00 is aggregated. Let's say that the metrics aggregation finishes at 15:05. The server receives a measurement report at 15:06 that contains timestamps from the 14:00 hour. This is a late measurement report because aggregation has already been run for the time slice of the reported data.

That raw data will get persisted, but in general it will not get aggregated, meaning we will not generate 1 hr, 6 hr, and 24 hr metrics for it. I say in general because it is possible through a server restart that the data could get aggregated.

We need to handle late data because late measurements are not only possible, they are probably fairly common. Work has already been done in master to address late data. https://docs.jboss.org/author/display/RHQ/Aggregation+Schema+Changes describes the changes.

Here is the squash commit in master for the work,

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 John Sanda 2014-06-28 15:09:13 UTC

I will help QE with establishing test cases. There are a number of different scenarios that have to be covered. For example, if the 6 hr time slice for late data has already passed, then we need to recalculate the 6 hr aggregate as well as the 1 hr aggregate.

Comment 2 John Sanda 2014-06-28 17:50:24 UTC

I want to point out that we cannot back port the changes to 3.2.x because there are substantial changes including schema changes. If we want to this in 3.2.x, then we need a separate BZ to track that effort.

Comment 3 John Sanda 2014-09-05 21:45:13 UTC

The initial work has been available since ER01, but I am setting the target milestone to ER03 because the changes for bug 1135604 and bug 1135630 impact this.

Comment 5 John Sanda 2014-09-26 20:41:00 UTC

Changes have been pushed to the release/jon3.3.x branch.

Commit hashes:
2ee9abb58
26c00149d

Comment 6 Simeon Pinder 2014-10-01 21:33:35 UTC

Moving to ON_QA as available for test with build:
https://brewweb.devel.redhat.com/buildinfo?buildID=388959