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 > Steps for all collectors > Lookups > Using lookup tables

Using lookup tables

Table of contents
No headers

Each lookup table entry consists of a value range (Low ID/High ID) and a target identifier value. Table content is tied to a date range so there can be multiple revisions of table data.

The following shows an example of a lookup table called cc_table :

lookup_table.jpg

Each entry in the table (numbered 1 through N) describes a translation rule.

Column Description

Low ID

The lowest matching identifier value that will trigger this translation rule

High ID

The highest matching identifier value that will trigger this translation rule

Target ID

The output of the translation rule

Low and high ranges are based on the standard ASCII sorting format.

Selecting a Low ID specifies the low end of an input value. Selecting a High ID specifies the high end of the of an input value. Consider the account ID translation mapping in the cc_table example, which you could use to map server names to customers:

 Low ID

High ID

 Target ID

aa

az

Customer A

ba

zz

Customer B

The data you collect for your servers might include a host dimension. In a workbook, a Set Dimension from Lookup processor could use the cc_table lookup table to map the host values of your servers to an account ID (the Target ID in the cc_table lookup table), and then add the appropriate values to a dimension, in this case an accountId dimension.

set_dimension_from_lookup.jpg

Using the cc_table definition, when transformed, any identifier with a name of host and a value beginning with a, such as ak-server1 and ak-server2 , is mapped to account ID Customer A because the first two characters of the host values fall into the aa to az range. Any value beginning with c, such as ca-server1 and co-server1, is mapped to account ID Customer B because the host values fall into the ba to zz range.

Entries in the lookup table are NOT case sensitive.

In the third and last row of the cc_table example, the Low ID and High ID have no values:

Low ID

High ID

Target ID

   

Customer C

A table entry with empty low and high IDs will match any input. This last entry of the translation table represents the default mapping.

You can leave the High ID empty. For example:

Low ID

High ID

Target ID

aa

 

Customer A

ba

 

Customer B

will be interpreted as follows :

Low ID

High ID

Target ID

aa

aazzzzzz

Customer A

ba

bazzzzzz

Customer B

Because the letter z has the highest sort order.

Last modified

Tags

This page has no custom tags.

Classifications

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