Been vaguely following this thread and I have a question. Just to confirm, as I haven't touched ceilometer code in ages, the instance metric still exists? Or at least something like it?
We're currently using ceilometer as the data collection for our billing, and the instance metric is our primary way of billing for compute mainly because it tells us which instances exist at a given point in time. We further then use the metadata of that metric to get instance state (building, active, shutdown, terminating, etc) to determine if we should bill it. With the changes to ceilometer and the move to gnocchi I know we will need to rebuild how we handle billing data as we upgrade, but what I'm worried about is if gnocchi+ceilometer have some equivalent to the instance metric that will supply us with the same data, or do we now need to do our own notification monitoring... Basically what I need is time series data of, this instance was in this state from this period to that period, and if I query for a range I get the ranges or changes in that time series. Is something like that present, or if not would I be able to make something like that in gnocchi? That way I can then query for a time range and know what state changes occurred for a given instance. After my current project I think I may need to dig into gnocchi and ceilometer again because I'm so far behind where things currently are. :( On 02/11/16 17:01, Ganpat Agarwal wrote: > That's correct. > > We can have meters only for those things which we can measure like > cpu, memory etc. > > If we want to keep a count of instance creation and deletion, you will > need to monitor the events and look for specific event types like > compute.instance.create.end or compute.instance.delete.end. > > On Wed, Nov 2, 2016 at 2:42 AM, gordon chung <g...@live.ca > <mailto:g...@live.ca>> wrote: > > > > On 01/11/16 05:30 AM, Raghunath D wrote: > > My requirement is to get sample/counter with "instance" name ,with > > event_type *compute.instance.** > > we don't build instance meter anymore because it's not a meter as it's > not measuring anything. > > -- > gord > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev