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

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > ETL workbooks > Output fields for a collection

Output fields for a collection

This article explains how to use the Output Fields tab of the Advanced Configuration dialog box, which looks and works the same for most collectors, to map input data to CC Record fields as output. This process is called output mapping. Using the Add Row button above the Fields table, you add a row that creates one field in a CC Record that the collection writes.

How data is grouped into those records depends on the collector you are working with. For example, in an XML collection you specify a separate group of output fields for each XPath expression you create, and a CC Record is written for each element matching the expression.

Basic columns

These columns appear in the Fields table by default, and are enough for most use cases.

  1. Type: The type of CC Record field you are creating. It can be a dimension, a measure, the time usage started, the time usage ended, or the usage date. There is no need for separate start and end dates because data is collected for a single select date, so usage that spans more than one day is captured in separate CC Records for each of those days.
  2. Label: When Type is Dimension or Measure, the name of the dimension or measure you are creating. This column is ignored for other types or when Label Input is specified. When you leave this column blank, the name in the Input column is used as the label.
  3. Input: The retrieved item whose value to use as the value of the CC Record field. The name you use here depends on the collector you are working with. For example, for a vSphere Snapshot collection it would be a property of an entity; for an XML collection, an element. This column overrides Value.
  4. Value: A literal expression to use as the value of the CC Record field. This column is ignored when an Input is specified.
  5. Format: The format of a date, time, or number in the data source, to enable HPE Consumption Analytics Portal to parse it correctly.
    • Dates and Times: When Type is Start TimeEnd Time, or Usage Date, use this field to specify the format in which that date or time is provided, whether as Input or Value. You can specify any valid Java simple date format. For example, yyyyMMdd or HH:mm:ss. For information about Java simple date formats, see the Java documentation for the SimpleDateFormat class. When Format is not specified, the date or time is assumed to be in RFC 3339 format.
    • Numbers: When Type is Measureuse this field to specify the format in which the number is provided, whether as Input or Value. This is only needed when your data source does not provide numeric values in a numeric data type. For instance, you don't need to specify number formatting with an Excel data source. When Format is not specified, the number is assumed to be in US locale, using commas for grouping and a period for the decimal point.
      You can specify the format as one of the following. You cannot combine both:
      • A locale code: Use a two-digit ISO country code to specify the locale whose format the input number follows. For example, de allows HPE Consumption Analytics Portal to read numbers in German format such as 1.234.567,89.
      • A pattern: Use a Java DecimalFormat pattern to specify the position of different elements in a number. This allows HPE Consumption Analytics Portal to read a string written in scientific notation or that includes both letters and numbers. For information about DecimalFormat patterns, see the Java documentation on DecimalFormat. 
  6. Label Input: The retrieved item whose value to use as the name of the CC Record field. This column overrides Label.
  7. Required: Whether the field is required in every CC Record generated. When no value exists for a required field in a given record, the record generates an exception. When this occurs in sample data retrieved when editing the current workbook, it appears as a warning in the Collector Validation Status list.

Advanced columns

Use the Show Advanced option to show and hide these lesser-used columns in the Fields table.

  1. Label Prefix: A literal expression to prepend to Label.
  2. Label Suffix: A literal expression to prepend to Label.
  3. Cost Input: When Type is Measure, the retrieved item whose value to use as the measure's cost. This column is ignored for other types. Use it, along with Interval Input and Rate Input, to create a passthrough measure that does not require pricing to be defined in a rate plan.
  4. Interval Input: When Type is Measure, the retrieved item whose value to use as the measure's charge interval. This column is ignored for other types. Valid values are MONTHLY, DAILY, and HOURLY.
  5. Rate Input: When Type is Measure, the retrieved item whose value to use as the measure's rate. This column is ignored for other types.

Examples

The following screenshot shows some XML input data, output field mappings for it, and the resulting output data.

Screenshot of output field mappings
(Click image to enlarge)

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP