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

Bug 1189621

Summary:	[RFE][ceilometer]: ability to set a severity level on the alarm in ceilometer
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-ceilometer	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED ERRATA	QA Contact:	Yurii Prokulevych <yprokule>
Severity:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	eglynn, jruzicka, markmc, pbrady, sgordon, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ceilometer/+spec/ceilometer-alarm-level
Whiteboard:	upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-ceilometer-2015.1.0-2.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:20:19 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:
Bug Depends On:	1232163
Bug Blocks:

Description RHOS Integration 2015-02-05 14:13:57 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/ceilometer-alarm-level.

Description:

Currently alarms in ceilometer have no concept of an importance level. This makes it hard from auditing stand point to figure out which alarm is a low priority vs critical. The goal of this blueprint is to incorporate the alarm_level into the alarm object so we can set a criticality. 

Specification URL (additional information):

https://github.com/openstack/ceilometer-specs/blob/master/specs/kilo/ceilometer-alarm-level.rst

Comment 2 Yurii Prokulevych 2015-04-16 08:23:05 UTC

Eoghan,
could you please review the above test plan and provide your comments?

Thank you in advance.
Regards,
Yurii

Comment 6 Yurii Prokulevych 2015-07-17 15:39:58 UTC

Verified according test plan.

Comment 8 errata-xmlrpc 2015-08-05 13:20:19 UTC

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://access.redhat.com/errata/RHEA-2015:1548