Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1042267

Summary:	[RFE][ceilometer]: Exclude aggregates with anomalously low sample counts from alarm evaluation
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-ceilometer	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, jruzicka, markmc, pbrady, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ceilometer/+spec/exclude-low-sample-count
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 RHOS Integration 2013-12-12 21:35:17 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/exclude-low-sample-count.

Description:

Currently we have a potential scenario whereby an autoscaling alarm defined over an instance group, with the evaluation window & cooldown policy both on the short side, may fire prematurely if an outlier instance is one of just a small number reported as yet for the current period.

We should detect the case where the sample count is anomalously low for the most recent datapoints, based on say a variance of at least one standard deviation from the observed norm. In that case, the less reliable datapoint should be excluded from consideration for alarming.

Specification URL (additional information):

None