Bug 600380

Summary:	Allow to pinpoint one border of a baseband
Product:	[Other] RHQ Project	Reporter:	Heiko W. Rupp <hrupp>
Component:	Monitoring	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.0	CC:	hrupp, jshaughn
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-26 10:19:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Heiko W. Rupp 2010-06-04 15:28:15 UTC

Baselines are auto calculated from existing measurement values in a way that the largest
value of some past inverval server as new high and low border of the band. 
New suspect metrics are now reported relative to this widened band. 
At the end it means that band could get one alert per week for a violation of one border and the next week that band is widened again.

It should be possible to say that the upper or lower border should stay constant at some value (or allow for narrowing). So that the band does not widen in that direction.

Comment 1 Corey Welton 2010-09-24 12:54:26 UTC

Triaged 21-Sept

Comment 3 Heiko W. Rupp 2014-06-30 12:45:46 UTC

Yes, I think this is still relevant.

Comment 4 Heiko W. Rupp 2014-09-26 10:19:40 UTC

Even with my comment #3, the case is like in Bug 620596 : we should concentrate on better algorithms in the future.