Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Configuring and Administering Azure > Onboarding Azure FC Customers > Creating an Azure Customer Workbook

Creating an Azure Customer Workbook

An ETL (extract-transform-load) Workbook is where you configure the collection, transformation, and publishing of data into the Cloud Cruiser database.  A Workbook can contain one or more Collections, each of which is a set of instructions for collecting a specific set of data from a single data source.

A Workbook also contains one or more Sheets, similar to sheets in a Microsoft Excel file.  A Sheet contains a Flow (a progression of steps that process data) and a grid that displays sample data so that you can see the results of each step as you develop it.  You can add to the Flow whichever steps you need to manipulate your collected data, but the Flow will most often start with an Import Collections step, which brings rows of data from one or more Collections into the Sheet so that they can be processed and most often end with a Publish Data step, which publishes the rows of data to a schema in the Cloud Cruiser database.

Azure Workbooks for HPE FC

Global Workbooks perform common tasks prior to invoking the customer-specific Workbooks, which simplifies the creation and maintenance of those jobs.

Global Workbooks

Global Workbooks are used to perform global tasks or tasks that are common to all customers.  Generally, these Workbooks are the first to run on any new processing day as they prepare data for the other Workbooks to use.

The running of the Schedules for these Workbooks is described in Loading Azure Usage and Charge Data.

The following are those used by Azure customers:

  • _Azure, which imports the data that was collected via the CREST API and then applies the common processing such as setting the Buy Cost based on the Buy Rate, determining which free Azure services are still within the free time period, etc.
  • _AzureBudgets, which queries the Cloud Cruiser database for the month-to-date charges of each customer and sends alerts to those customers' contacts if budget thresholds have been exceeded
  • _ProcessUsage, which parses the usage files into the ${env.processDir}/_byCustomer directory, within a directory specific to each customer.  With this structure, customer-specific Workbooks need only a single Collection to retrieve customer-specific usage files.

Customer-Specific Workbooks

Customer-specific Workbooks process usage data for specific customers and publish it to the Cloud Cruiser database.  They are created from the FC Customer Template workbook template.  This template contains a number of Sheets for each type of resource supported by FC; however, the only two required for Azure customers are as follows:

  • AzureUsage, which applies customer-specific discounts and publishes the data to the Cloud Cruiser database.
  • AzureTiers, which applies any tier discounts and publishes the data to the Cloud Cruiser database.

In order to create a customer-specific Azure Workbook, follow the steps at Creating a Workbook and delete all but the two AzureUsage and AzureTiers Sheets in Step 5.

Configuring a Customer Collection

Once the customer-specific Workbook has been created, configure the corresponding collection as described in Configuring a Collection starting at Step 4 as the Workbook is already open.

Referencing the Customer Discount Lookup Table

This is only necessary if the customer has discounts that differ from those that apply to all customers and the Lookup Table was created in Creating the Azure Customer Discount Lookup Table.

The Workbook template includes a reference to the common 00000_AzureServiceDiscounts Lookup Table for both the Discount dimension (i.e., the common discount) as well as the CustomerDiscount dimension.  However, each customer will have to specify its customer-specific discount Lookup Table created at Configuring Azure Lookup Tables.

To Change the Reference to the Customer-Specific Discount Lookup Table

  1. Expand the Apply Customer Discount Step in the AzureUsage Sheet.
  2. Double-click the second Processor.
  3. Change the Lookup Table from 00000_AzureServicesDiscount to the customer-specific discount Lookup Table created at Configuring Azure Lookup Tables.
  4. Click OK.
  5. Click Save to save the Workbook.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.

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