Bug 1261029 – [RFE] Allow alarms to be tirggered by the receipt of a notification event

Bug 1261029 - [RFE] Allow alarms to be tirggered by the receipt of a notification event

Summary:	[RFE] Allow alarms to be tirggered by the receipt of a notification event

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-aodh (Show other bugs)
Sub Component:
Version:	8.0 (Liberty)
Hardware:	Unspecified Unspecified

Priority	high Severity unspecified
Target Milestone:	beta
Target Release:	8.0 (Liberty)
Assigned To:	Eoghan Glynn
QA Contact:	Yurii Prokulevych
Docs Contact:

URL:	http://specs.openstack.org/openstack/...
Whiteboard:	FutureFeature
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-08 08:55 EDT by Eoghan Glynn
Modified:	2016-04-07 17:06 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	openstack-aodh-1.0.0-3.el7ost
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-04-07 17:06:52 EDT
Type:	Bug
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.)

Groups: None (edit)

Description Eoghan Glynn 2015-09-08 08:55:44 EDT

Previously, alarms could only be triggered by the observed trend of some statistic crossing a static threshold.

It would be useful to allow alarm rules to also be defined over the occurance of some event, so that when a corresponding notification is received, the alarm fires in the usual way.

Comment 4 Yurii Prokulevych 2016-03-08 10:20:10 EST

Verified according test plan with aodh*-1.1.2-1.el7ost.noarch

Comment 6 errata-xmlrpc 2016-04-07 17:06:52 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0603.html

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