Red Hat Bugzilla – Bug 1182275
[RFE] wildcarding api for mass-statistics
Last modified: 2015-09-10 06:14:27 EDT
Further to bug #1059783, it would be nice if the /statistics queries in the REST API had a mode whereby the server/engine iterated across objects to return one bulk response, rather than (what I believe is) the current requirement to enumerate each target object, one per request. So, for example, please consider supporting not just: GET /api/hosts/{host:id}/statistics GET /api/vms/{vm:id}/nics/{nic:id}/statitics but also something like: GET /api/hosts/*/statistics GET /api/vms/*/nics/*/statistics and the xml/json results would naturally contain nested structures, identifying the respective {host:id} or {nic:id} etc. with a nested tag.
Doing this is extremelly complicated as it breaks the assumption that one URI maps to one resource. Supporting that wildcard may just be impossible with Resteasy. Anyhow I'm targeting for 4.0 for later reconsideration.
OK, until the point where you can reference a group of resources under one URI / HTTP request, what is the preferred method for fetching stats about all the resources? A list-all-objects call then N separate per-object calls?
(In reply to Frank Ch. Eigler from comment #2) > OK, until the point where you can reference a group of resources > under one URI / HTTP request, what is the preferred method for > fetching stats about all the resources? A list-all-objects call > then N separate per-object calls? Yes, that is the only way.