Replies: 1 comment 1 reply
|
You can clear the old usage records without cleaning or rebuilding your production cloud database. I don't recommend truncating the entire cloud_usage database because it also contains internal helper and usage-job information. Removing everything may cause CloudStack to process old usage events again. If you simply want to remove the old usage history and start collecting new records, I recommend: Step 1. Stop the Usage Server. TRUNCATE TABLE cloud_usage.cloud_usage; Step 4. Start the Usage Server again. This keeps the existing Usage Server state/helper tables while removing the old generated usage records. I would also recommend taking the database backup first, especially if the usage data is currently being used by any billing or quota integration. Nick R |
Uh oh!
There was an error while loading. Please reload this page.
Hi!!
How can I cleanup my cluod_usage database?
I don't care to loose old records, I just want to start recording usage from now on.
I cannot cleanup my cloud database, its in production. I just want to clean the cloud_usage.
Thanks
All reactions