OpenStack Telemetry (Ceilometer)

Support the storing of raw events

Registered by Sandy Walsh on 2013-04-24

There are many use-cases that require the storing of the underlying raw event from the source systems. This feature will provide a flexible storage mechanism for this varied data.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
None
Direction:
Approved
Assignee:
Sandy Walsh
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Sandy Walsh on 2013-05-01
Completed by
Julien Danjou on 2013-05-27

Related branches

Sprints

Whiteboard

Sandy: quick question - The event table you are adding in, how you are going to store the data? via normal pipleline(MQ) or via UDP publisher/Collector ? and is it going to share the same schema with Meter? -Shengjie

Hey Shengjie! It'll be something like the schema outlined here: https://etherpad.openstack.org/Supporting-rich-data-types .. the events will be those coming in from the Collector (aka the Nova event notifications). The raw json of the event will also be stored, but this will likely be done in a separate table. Meters will point to the underlying Event (if available). Events are different than Meters in that they generally aren't measurements, they're just points in time where things happened ... but Meters can be derived from Events. Hope it helps! -S

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-event-table,n,z

Addressed by: https://review.openstack.org/29112
    Add Event methods to db api.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.