Difference between revisions of "Accounting Aggregator"
From Gcube Wiki
Luca.frosini (Talk | contribs) |
Luca.frosini (Talk | contribs) |
||
| Line 19: | Line 19: | ||
| − | == How to manage | + | == How to manage calledMethod lead to ServiceUsageRecord can not be aggregated == |
| + | |||
| + | RESTFull (and RESt-like) services contain the ID of the managed resource inside the path of the URL. Smartgears auto calculate '''calledMethod''' by using the relative path of the URL. | ||
| + | This lead to have ServiceUsageRecord can not be aggregated. | ||
Revision as of 11:10, 2 January 2018
This component is responsible of aggregating the collected Accounting data.
Accounting Aggregator in the Accounting Architecture
The following image evidences the accounting-aggregator components as part of Accounting Architecture:
Accounting Aggregator Execution
This component is a Smart Executor plugin and is launched as Global Scheduled Task (see Smart Executor for further information)
It aggregates (lossless) accounted Usage Record. The scheduling plan is to run on different smart-executor equipped with this plugin with the following parameters:
- Hourly => accounting records per hour are available for the past week;
- Daily => accounting records per day are available for the past 3 months;
- Monthly => accounting records per month are available for the past 3 years;
- Yearly => accounting records per year are available for the past 10 years;
How to manage calledMethod lead to ServiceUsageRecord can not be aggregated
RESTFull (and RESt-like) services contain the ID of the managed resource inside the path of the URL. Smartgears auto calculate calledMethod by using the relative path of the URL. This lead to have ServiceUsageRecord can not be aggregated.
