Open Stack

On Tue, Jan 29 2013, Angus Salkeld wrote:

> Nice walk through, I need to try digest how that is all going to fit together.
>
> It initially seems to me that there is a new entity "Notification/TracePoint"?
> They don't really seem like meters, and it might make sense to just model
> correctly rather than trying to squeeze them into meters.

+1

From what I understand from your video, StackTach logs raw notifications
and then feed data into a few tables, doing some computing.

So what it does is down to:
1. Stock raw notifications
2. Compute values from these notifications and cache them (= store them
   into a few tables)
   Some of these values might be meters.

I don't think Ceilometer collector is going to store raw notifications.
There's no point into the whole Ceilometer project to store this data.

Your best call here is probably to keep that part of StackTach if you
really need all the raw notifications.

For things are likely to be meter (i.e. things with a duration and/or a
volume), you can write some Ceilometer notification plugin building a
bunch of meter from what you get. Multi-publisher can also help you
building more advanced counter through the use of transformer if you
wish.

-- 
Julien Danjou
;; Free Software hacker & freelance
;; http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130130/7f84c0a5/attachment.pgp>