[
https://issues.apache.org/jira/browse/CLOUDSTACK-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi resolved CLOUDSTACK-7510.
-----------------------------------------
Resolution: Fixed
Updated Branches:
refs/heads/master 75cd79a23 -> 70142c4ac
Added "usageid" parameter to the "listUsageRecords" API call. Can be used only
together with "type" parameter specified
Signed-off-by: Ilia Shakitko <[email protected]>
Signed-off-by: Rohit Yadav <[email protected]>
Commit:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=70142c4acb84a2d2b1fe8806c159493e4a556532
> Add "usageid" parameter to the "listUsageRecords" API call
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-7510
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7510
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server
> Reporter: Ilia Shakitko
> Priority: Minor
> Fix For: 4.5.0
>
>
> Working with Usage server and usage records very often I need to get only
> records for that particular usage ID. For example when filtering out
> network_bytes_received/sent with big amount of data it's not very fast to
> process hundreds of objects looking for the only one you need.
> It would be useful to have an ability to filter out usage records only for
> specific resource ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
