Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Windows Azure Pack > Flows in the Microsoft Windows Azure Pack template

Flows in the Microsoft Windows Azure Pack template

Table of contents
No headers

The Microsoft Windows Azure Pack workbook includes several flows that consolidate subscription, usage, and resource ownership information to a simple format that allows you to understand how to charge for the actual usage of specific Windows Azure Pack services.

For detailed information about the raw data collected from Windows Azure Pack, see Dimensions and measures collected from Windows Azure Pack.

Flow Description
Ownership Imports data from the ResourceOwnership collection, correlating resources with the departments that own those resources. If the collected data does not contain Department data, the flow creates a lookup file that allows other flows to associate departments to resource IDs.
ImportCustomers Imports Windows Azure Pack subscription data from the Subscription1 collection. It populates the Department dimension, correlates collected information with subscription information collected from the previous day, and aggregates subscription information to combine newly collected subscription rows. This correlation and aggregation prevents redundant subscription information from being used in Cloud Cruiser, and speeds the processing time for Cloud Cruiser displays and reports. The flow creates lookup files containing subscriber and subscription name information to be used by the Usage flows. The flow then aggregates and publishes subscriber information.​

The Windows Azure Pack workbook uses the following flows to transform and publish usage data to Cloud Cruiser. These Usage flows perform the same basic functions, each for a different type of data collected from Windows Azure Pack.

  • Usage_Systemcenter
  • Usage_Webspaces
  • Usage_Sqlservers
  • Usage_Mysqlservers

The flows import data from the Usage1 collection, and remove all rows of data not relevant to the data type they are designed to process. For example, the Usage_Systemcenter flow removes all rows not related to Microsoft System Center.

The flows remove the row for Subscription ID 75700cd5-893e-4f68-ada7-50ef4668acc6, which is always present in Windows Azure Pack, but which is not relevant to your actual usage. If Subscription ID 00000000-0000-0000-0000-000000000000 is present in the collected data, the flows set the SubscriberSubscriptionName and Department dimensions of that row to a value of Administrator.

The flows obtain subscriber and subscription name information from the lookup files created by the ImportCustomers flow to associate that data with specific instances of usage.

The Usage_Systemcenter flow has additional transformation processes. It converts allocated disk size data to GB. It also calculates VM sizing data, and then compares that data to standard VM sizes defined in the lookup tables you imported. For VMs that fall outside of the definitions in the lookup table, the flow marks those records as nonstandard.

When transformation is complete, the Usage flows publish their data to the Infratructure schema.

HandleUnknowns Alerts you about any resources that do not have assigned owners and departments. It imports data from the ImportCustomers and Usage datasets, and then scans the Department and Owner fields for a value of Unknown. For every Unknown value, the flow generates an exception message visible in the Data > Processing > Monitoring area of Cloud Cruiser.
Last modified


This page has no custom tags.


This page has no classifications.

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