![]() |
Consumption Analytics Documentation |
Resetting data ensures that all usage for a given date or later can be matched with a subscription, allowing charges to be loaded. You should reset data when collecting from Windows Azure Pack for the first time or as part of troubleshooting a problem. If you just need to recover from a period where collection failed for some reason, instead see Recovering after a period with no collection.
The reset process makes all subscriptions and plans that were active on that date appear in the state file for that date so that the load job can roll them forward one day at a time. Without this, subscriptions and plans created before the chosen date are overlooked and usage associated with them cannot be charged.
Before you begin
Ensure that you have a data source with a working connection.
To reset Windows Azure Pack data
<working_dir>/usage_files/azure_pack
on the Cloud Cruiser server. azure_pack_collect
job. bootstrap=true
, then click Run batch job.bootstrap
argument makes it collect all existing subscriptions and plans. On nightly runs, the job collects only notifications of changes to your subscriptions and plans. Job azure_pack_collect failed
, click Yes to view the log. azure_pack_daily_load
job, then in the End Date field, enter or select yesterday’s date. Leave the Start Date that you set in step 7.Charges for usage from your chosen date through yesterday are now viewable, and you can resume scheduled nightly execution of both jobs.
You will not see charges for subscriptions or add-ons, and might not see charges for some usage that you can verify in Windows Azure Pack. For more information, see Which cost data is available and when.
(c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP