Bug 600380 - Allow to pinpoint one border of a baseband
Summary: Allow to pinpoint one border of a baseband
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Monitoring (Show other bugs)
(Show other bugs)
Version: 3.0.0
Hardware: All All
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-04 15:28 UTC by Heiko W. Rupp
Modified: 2014-09-26 10:19 UTC (History)
2 users (show)

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.