Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > Microsoft Windows Azure Pack > Which cost data is available and when

Which cost data is available and when

This topic explains the types of charges you will see and not see, when charges will appear in the Cloud Cruiser Portal and Windows Azure Pack portals, and how to troubleshoot when expected VM data is not collected.

Types of charges

Based on the pricing you specify, Cloud Cruiser applies charges to the usage of Windows Azure Pack services. So you will see charges for usage related to databases, websites, and virtual machines, such as the following examples:

  • SQL Server Space Allocated
  • Incoming Request Bytes (for a website)
  • VM CPU Allocated

By default Cloud Cruiser does not compute charges for subscriptions to Windows Azure Pack plans or for add-ons purchased for those subscriptions, only for usage of the services offered by each plan. If you want to charge for these things, you can create the appropriate resources and modify the load job to set values for those resources from collected data.

When charges become visible

The costs you see in the Cloud Cruiser Portal and Windows Azure Pack portals are not real-time information. At 2:15am every night, Cloud Cruiser collects subscription and usage data for the previous day from the Windows Azure Pack Usage API. Therefore, if a VM is created on Monday you won’t see costs for that VM until Tuesday morning.

Troubleshooting a lack of VM data

If collection jobs are completing without errors but failing to collect data for virtual machine usage, it’s possible that the data is not available in Windows Azure Pack to collect.

Ensuring Windows Azure Pack is configured correctly

There are several components that provide data on VM usage to Windows Azure Pack, and if they are not configured correctly this data is not placed in Windows Azure Pack’s usage database where it can be collected by Cloud Cruiser or Cloud Cruiser Express.

The following series of Microsoft blog articles explains the components involved and how to configure them:

  1. IaaS Usage and Service Reporting using System Center 2012 R2 and Windows Azure Pack
  2. Configuring VMM and OM for IaaS usage and metering
  3. Configuring SPF and Windows Azure Pack for IaaS usage and metering

The series contains four articles, but only the three listed here are relevant to making data available to Cloud Cruiser or Cloud Cruiser Express.

Additionally, see the following Microsoft blog articles for troubleshooting Windows Azure Pack and the collection of usage data:

  1. Troubleshooting Windows Azure Pack & Usage (Part 1)
  2. Troubleshooting Windows Azure Pack & Usage (Part 2) 

Resetting data collection

If you are not seeing usage data after installing Cloud Cruiser Express, it may be because usage data was not available from the Windows Azure Pack system at the time of Cloud Cruiser Express installation.

This procedure loads yesterday's usage and all subscriptions and plans that existed on or before yesterday (previous day). The scheduled jobs will collect every night, so each day's usage is available the next day. 

To reset data collection

  1. On the server hosting Cloud Cruiser Express, navigate to the Cloud Cruiser installation directory.
  2. Delete the folder <cc-working>/usage/azure_pack/**/* 
  3. In Cloud Cruiser Express, navigate to Data > Job Loads.
  4. Delete any data loads by selecting Select All > Delete Loads.
  5. Navigate to Data > Scheduling.
  6. Select the job named azure_pack_collect.
  7. Set the Select Date to Previous Day.
  8. Enter the following in the Arguments field, and then click Save:
  9. Click Run Now.
  10. Set the Select Date back to Current Day.
  11. Clear the Arguments field and then click Save.
  12. Select the job named execute azure_pack_daily_load.
  13. Ensure that the Select Date is set to Previous Day.
  14. Ensure that the Arguments field is empty and then click Run Now.

Last modified


This page has no custom tags.


This page has no classifications.

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