On 2017-12-04 08:53 AM, Julien Danjou wrote: > Which is usually a problem because of the APIs, not Ceilometer. They're > sometimes utterly slow for simple things and other times don't offer a > way to retrieve what Ceilometer needs in a batch-y way. > >> in general, there's a preference that stats be pushed to ceilometer >> rather than pulled. > Yes, but for the wrong reasons. Having a component sending a batch of > notification every hour without any configuration knob and granularity > choice is a PITA for the users. Plus it ususally comes from a single > point (of failure?).
well you can configure it, just at a per service level.. but that's a fair point. > > Ceilometer would do a better job than $project at getting this info, if > said project(s) would offer a proper and performant API to retrieve them > efficiently. but at the end of the day, are you building for reality or for some personal ideal scenario? :p is there a service that offers a stats endpoint? -- gord __________________________________________________________________________ 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
