gnocchi dispatcher should leverage events

[gordon chung]

gnocchi can track end time of a resource. we don't actually set this in ceilometer so gnocchi resources are never closed.

[Sergio Colinas (sergio-n)]

Is anyone working on this? We also need it to search for active resources for a timeframe.

[Trevor McCasland (twm2016)]

I would like to work on this but I need more guidance.

By saying "set this in ceilometer" do you mean you want to enable the dispatcher by adding the following section in the ceilometer.conf file?

[DEFAULT] meter_dispatchers = gnocchi

I tried looking for ceilometer.conf but it seems to me that this is something that is made after installation, so if that is true how would I make it so it is included in the file?

[Nicolas Vila (nvlan)]

Hello Trevor,

On our ceilometer.conf we have "dispatcher = gnocchi" and then configure gnocchi's parameters in the [dispatcher_gnocchi] section, and then the ceilometer-collector pushes the samples taken by the agents to the gnocchi-api.
Gnocchi has the capability to store both the timestamp of when a resource was created as well as a second timestamp of when the resource dissapears (eg. when an instance is terminated), however ceilometer is not informing gnocchi of the last, and when you query gnocchi for all instance metrics within a timeframe, the reply contains resources that no longer existed within that timeframe.

I'm usually logged in on #openstack-telemetry if you need any further clarification, and we have several labs/deployments where to test.

Thanks, regards.

[Mehdi Abaakouk (sileht)]

For notice, a PoC have been done here: https://review.openstack.org/#/c/217017/
And can be a base for this.