Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Steps for all collectors > Translation process

Translation process

Table of contents
No headers

Translation is the process of translating identifier values from one schema to another by using a table that maps input values (or ranges of values) to output values. Translation is used in the transformation step of a job, for example, to convert part of a VM name into a string that makes up part of the account identifier against which usage will be charged.

This section contains the following articles:


During the transformation process, collection scripts will often require the use of one or more translation steps. For each record processed by a collection script, the value of the source (input) identifier is compared to each table entry, in order, until it finds a match or reaches the end of the table. These comparisons are only made for the number of characters provided by the translation table. For example, if the input value is shorter than the low identifier value in the table, then it will not be a match.

In the case of a match, the value for the first matching row is used to create or update the target identifier in the current record. In the case of NO match, the behavior depends on the exception processing settings configured in the collection script. For more information, see Exception processing.

Last modified


This page has no custom tags.


This page has no classifications.

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