Open Stack

Thanks for your reply.

1.Actually, statistics is used by horizon now to render the tables and
grouping by resource is needed. The number of http requests should be
reduced to speed up the page loading.

2. /statistics can't do this. You know, horizon may need hundreds or
thousands of value to render a chart. it's a disaster if so many requests
is sent to ceilometer api to render one chart.


On Tue, Jul 23, 2013 at 8:54 PM, Julien Danjou <julien at danjou.info> wrote:

> On Tue, Jul 23 2013, Brooklyn Chen wrote:
>
> >
> > It would be helpful if ceilometer-api provides following api:
> >
> > GET /v2/usages/disk/
> >
> > Parameters:  q(list(Query)) Filter rules for the resources to be
> returned.
> > Return Type: list(Usage) A list of usage with different tenant,user,
> > resource
> >
> > GET /v2/usages/disk/<usage_id>
>
> Did you try /v2/meter/<meter-id>/statistics ?
> I think /statistics is good enough *except* that it misses the ability
> to group by resource the statistics.
>
> > 2. need gauge data like "cpu_util" to render stat charts.
> > We have cumulative meters like "disk.read.bytes" and
> > "networking.incoming.bytes" but they are not able to be used for drawing
> > charts since the value of them are always increasing.
>
> The /statistics with the period= argument would allow you to do that as
> far as I can tell.
>
> --
> Julien Danjou
> # Free Software hacker # freelance consultant
> # http://julien.danjou.info
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130725/10d99d08/attachment.html>