openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #24693
Re: [OpenStack] [Metering] Options to obtain Notifications when ceilometer generates a meter entry in the DB
Doug, Deepak,
I am also in the process of implementing a blueprint which allows one
to easily add a dispatcher to do whatever you want to do for each meter
received by Ceilometer. Here is the link to blueprint and the
implementation.
https://blueprints.launchpad.net/openstack/?searchtext=multi-dispatcher-enablement
https://review.openstack.org/#/c/34301/
If this gets merged soon, you will only need to write something like
dispatcher_log.py, in method record_metering_data you may choose to do
whatever you like to do with the meter data. For your question #1, you can
simple fire up a text message or send out an email if you prefer. Even
though you can do whatever you want to do there, but make sure the method
is extremely light weight and effecient.
Thanks.
Tong Li
Emerging Technologies & Standards
Building 501/B205
litong01@xxxxxxxxxx
From: Doug Hellmann <doug.hellmann@xxxxxxxxxxxxx>
To: Deepak Bangalore Hariyanna <dbangalo@xxxxxxx>,
Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
Date: 06/25/2013 03:23 PM
Subject: Re: [Openstack] [OpenStack] [Metering] Options to obtain
Notifications when ceilometer generates a meter entry in the DB
Sent by: "Openstack" <openstack-bounces
+litong01=us.ibm.com@xxxxxxxxxxxxxxxxxxx>
On Fri, Jun 21, 2013 at 9:37 PM, Deepak Bangalore Hariyanna <
dbangalo@xxxxxxx> wrote:
Hi All,
I am currently working on an charging application to work with ceilometer
(Grizzly release).
Have been working on openstack for just couple weeks and hence have a
couple of questions:
1). I read in the documentation that the only way to access the data
generated by collector is through the API(i.e either use the cURL option
or the ceilometer pythonclient to query the required information). I am
able to do this and fetch the required data.
However, for an application to access these, is there a better way? Like,
whenever the ceilometer generates an event entry in the db, does it
provide any notification on any queues, or is there a way we can
configure this to happen?
If there is no such option, I plan to periodically poll the ceilometer
through API for the usage data. (which I sincerely feel is a bad idea).
2). From the Havana roadmap, I see an objective "Publish meters to other
systems"
Does this mean, other systems can configure to bind themselves on an AMQP
queue and ceilometer would publish notifications on this exchange?
If so, this would be a feature of Havana?
Because I was confused with the publisher feature of Grizzzly, as below
Would be great if someone can help me on this.
The architecture of ceilometer supports plugging in different publishers.
We have one that reproduces the grizzly/folsom feature of sending data on
the message bus so the collector can receive it. We also have one that
sends UDP messages that are consumed by the collector (useful for
monitoring, but not for metering). The API is designed to allow you to
write your own if you have a custom consumer, and we would welcome other
reusable publishers in the core code base.
Doug
Thanks a lot,
Deepak
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
References