Hello, Ceilometer Team, For now, the results listing meters are not grouped, even we can filter the results by resource_id, project_id or meter_name, but I don't think this is a good way to group the meters.
See an example: suo@ustack:~/devstack$ ceilometer meter-list +----------------------------+-------+-----------+--------------------------------------+---------+----------------------------------+ | Name | Type | Unit | Resource ID | User ID | Project ID | +----------------------------+-------+-----------+--------------------------------------+---------+----------------------------------+ | image | gauge | image | 3e43b8f4-b347-42a4-b189-931fff9538f3 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image | gauge | image | 838f5bce-ce46-4241-88ba-d6bd1c267bf8 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image | gauge | image | b5fbf186-02fa-4279-a918-d71e6abd7020 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.size | gauge | B | 3e43b8f4-b347-42a4-b189-931fff9538f3 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.size | gauge | B | 838f5bce-ce46-4241-88ba-d6bd1c267bf8 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.size | gauge | B | b5fbf186-02fa-4279-a918-d71e6abd7020 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.update | delta | image | 3e43b8f4-b347-42a4-b189-931fff9538f3 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.update | delta | image | 838f5bce-ce46-4241-88ba-d6bd1c267bf8 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.update | delta | image | b5fbf186-02fa-4279-a918-d71e6abd7020 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.upload | delta | image | 3e43b8f4-b347-42a4-b189-931fff9538f3 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.upload | delta | image | 838f5bce-ce46-4241-88ba-d6bd1c267bf8 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | image.upload | delta | image | b5fbf186-02fa-4279-a918-d71e6abd7020 | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | storage.objects | gauge | object | 27ffe3121d4b49c19ebb51548ee7ea88 | None | 27ffe3121d4b49c19ebb51548ee7ea88 | | storage.objects | gauge | object | 2dc999e8e61e43748d3eb5c02b878fe1 | None | 2dc999e8e61e43748d3eb5c02b878fe1 | | storage.objects | gauge | object | 421212a8b3cb43da9eeae077f59c4e40 | None | 421212a8b3cb43da9eeae077f59c4e40 | ...... | storage.objects.size | gauge | B | 4a0d19f2e025447ea8567a0ccaf2f74a | None | 4a0d19f2e025447ea8567a0ccaf2f74a | | storage.objects.size | gauge | B | 61e13fab30f9493b814321e6684936a4 | None | 61e13fab30f9493b814321e6684936a4 | | storage.objects.size | gauge | B | b03b0bfc3ccb4dd98d4ad03c6d32e1be | None | b03b0bfc3ccb4dd98d4ad03c6d32e1be | | storage.objects.size | gauge | B | f22454605f2d498fad0b2b5520fba349 | None | f22454605f2d498fad0b2b5520fba349 | +----------------------------+-------+-----------+--------------------------------------+---------+----------------------------------+ I think this result will confuse users more or little, which meters come from compute service, and which meters come from network service, or can I get all the meters coming from storage service ? So I think the grouping by services will make users more clear about what they have got, and it is also usefull to display them on dashboard. In addition, there is a glossary named 'source' in ceilometer, but I don't think that is the same thing with grouping. So if we can add a field named service/group/namespace to the meter table, that will make the whole world clear. Any ideas ?
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
