OpenStack Telemetry (Ceilometer)

Alarm API

Registered by Eoghan Glynn on 2013-03-05

We need to tie down the requirements for managing the state and history of alarms, for example providing:

 * an API to allow users define and modify alarm rules

 * an API to query current alarm state and modify this state for testing purposes

 * a period for which alarm history is retained and is accessible to the alarm owner (likely to have less stringent data retention requirements than regular metering data)

 * an administrative API to support across-the-board querying of state transitions for a particular period (useful when assessing the impact of operational issues in the metric pipeline)

Blueprint information

Status:
Complete
Approver:
Julien Danjou
Priority:
High
Drafter:
Eoghan Glynn
Direction:
Approved
Assignee:
Angus Salkeld
Definition:
Drafting
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Angus Salkeld on 2013-05-02
Completed by
Julien Danjou on 2013-05-27

Related branches

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/alarm-api,n,z

Addressed by: https://review.openstack.org/27691
    Add just the most minimal alarm API

Addressed by: https://review.openstack.org/28007
    Add Alarm DB API and models

Addressed by: https://review.openstack.org/28008
    Add the mongo implementation of alarms collection

Gerrit topic: https://review.openstack.org/#q,topic:alarm-api,n,z

Addressed by: https://review.openstack.org/28010
    Connect the Alarm API to the db

Addressed by: https://review.openstack.org/28378
    Add the sqlalchemy implementation of the alarms collection.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.