Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Onboarding FC customers > Configuring a collection

Configuring a collection

Table of contents
No headers

A collection specifies the data to retrieve from the source and how to map it to Cloud Cruiser. Usage files are downloaded by a common workbook named _DownloadUsage. A second workbook, _ProcessUsage, converts the downloaded data to Cloud Cruiser Record (CCR) format, and performs some pre-processing in order to make customer-specific workbooks less complex. As part of the customer onboarding process, you must configure a customer-specific collection in your workbook.

To configure a collection

  1. Open your workbook for editing.
  2. In the Workbook area of your workbook, click Settings.
  3. Select a Select Date that you know has usage data for the customer (usually 2 days before the current day is good).
  4. In the Collections area of your workbook, click List.
    A list dialog box opens.
    collectionsList.jpg
  5. Select the CUSTOMER row, and then click Edit.
    The Edit Collection dialog box appears.
    editCollection1.jpg
  6. In the Collection Name field, replace CUSTOMER with a name representing the FC customer. For example, AceRun.
    This name must be unique in Cloud Cruiser.
  7. Under the Data Source field, click Create New.
    The fields change to allow you to enter information about the source of data for this customer.
    editCollection2.jpg
  8. In the Name field, enter a name for the data source, such as AceRun.
  9. In the File Name field, enter the following string:
    ${env.processingDir}/_byCustomer/<customer>/${env.selectDate}.ccr
    • The pattern ${env.processingDir} points at the location on the server were intermediate processing files are stored. This value is configured in the server’s Configuration settings, and on the FC implementation it is set to the value /mnt/cc-working/processing.
    • The <customer> string must match the customer alias found in the received metering files. Sometimes this is a friendly name such as AceRun.  Sometimes this is the account ID, such as HP-APJ-999-AUS-00021. This value was set by the person preparing the metering scripts on the FC customer’s on-premise equipment.  
    • The pattern ${env.selectDate} is a parameter that is replaced by the scheduler, and refers to the date (in yyyymmdd format) on which the process is run. For example, if the date is May 26, 2015, the ${env.selectDate} parameter is replaced with 2015026.
    For example, for the customer AceRun, the File Name field would contain the following string: ${env.processingDir}/_byCustomer/AceRun/${env.selectDate}.ccr

    editCollection3.jpg
  10. (optional) Click Test to test the data source parameters.
    For example, if the path in the File Name field is incorrect, you should identify that before attempting to load customer data.
  11. Click Finish to save the data source.
  12. Click Save to save your progress in the workbook.

To configure a fixed charge collection

For fixed charges, a special collector needs to be added to the workbook:

  1. In the Collections box on the top panel of the workbook, click the New icon
  2. Select CSV/Flat File
  3. Set Collection Name to NNNNN-FixedCharges, where NNNNN is the customer ID.
  4. Select the Data Source Instance.
  5. Click on the Advanced link in the bottom left of the collection screen and select the Output Fields tab.  Change the type for Instance to Measure.
  6. Click Finish to save the collector.
  7. Edit the Import Collections step in the FixedCharges sheet and select the collection just created (NNNNN-FixedCharges).
  8. Click the save icon to save the workbook.
Last modified

Tags

Classifications

This page has no classifications.

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