Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > Microsoft Windows Azure Pack > Resetting data to enable daily collection

Resetting data to enable daily collection

Table of contents
No headers

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

  1. If you have not previously collected Windows Azure Pack data, skip to step 5. Otherwise, continue.
  2. If you are using Cloud Cruiser 3.3 or later, skip to step 3. Otherwise, delete the directory <working_dir>/usage_files/azure_pack on the Cloud Cruiser server.
  3. In the Cloud Cruiser Portal, navigate to Data > Job Loads.
  4. Clear the date range for the Accounting Date column. If there are any loads listed in the table, delete them all.
    For more information, see Deleting load tracking data.
  5. Go to Data > Job Maintenance.
  6. In the Production Jobs list, select the azure_pack_collect job.
  7. In the Start Date field, enter or select the first date for which you want to charge for Windows Azure Pack usage.
    The End Date field is automatically set to match.
  8. In the Arguments field enter bootstrap=true , then click Run batch job.
    The collect job runs. The 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.
  9. If the completion dialog says Job azure_pack_collect failed , click Yes to view the log.
    For information about viewing job logs, see Monitoring job results. When you have corrected the problem and run the collect job successfully, continue to the next step.
  10. Select the 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.
    This sets a date range starting with the date against which you ran the collect job. The load job will run against each date in this range in succession, comparing the plans and subscriptions in the state file for that date against the plan and subscription events collected and then rolling over the correct list of active plans and subscriptions to the state file for the following date.
  11. click Run batch job.
    The load job runs. If this job fails, troubleshoot it as described in the previous step until it completes successfully.

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.

Last modified



This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP