Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > Cisco IAC > Mapping data to Cloud Cruiser

Mapping data to Cloud Cruiser

The Cisco IAC Collector generates XML data that you can map to CC Record output using XPath expressions and standard output field mapping. This works the same as does mapping output from the XML Collector. For information about mapping output for that collector that also applies to Cisco IAC data, see Mapping data to Cloud Cruiser.

The subscription documents are relatively simple and data is mapped at the root level for common attributes. Mapping is also based on XPath expression(s) for nested attributes specific to the service type. In most cases, using a single expression to capture all nested attributes is sufficient.

Feed configuration

The feed configuration for IAC Portal collection extends the XML feed configuration and adds a property for an optional subscription filter. For more information on filters, see the "Filters" reference in the REST API section of the Cisco Service Portal Integration Guide .

Examples of subscription filters

ServiceItemTypeName=Virtual Machine (VM)|OR|ServiceItemTypeName=Virtual Server Snapshot
ServiceItemClassificationName=Virtual Applications and Servers

Time and date

All records produced reflect the job’s selectDate parameter as the usage end date. After aggregation, the usage is assumed to be for the entire day (24 hours). The minimum interval supported for calculation of charges is 1 day.


Each subscription document has the following common elements that are typically mapped as identifiers:

  • serviceItemClassificationID
  • serviceItemClassificationName
  • serviceItemTypeID
  • serviceItemTypeName
  • organizationalUnitID
  • organizationalUnitName
  • customerID
  • customerName
  • requisitionID
  • requisitionEntryID
  • serviceItemID

In addition to the common elements, you can map attributes specific to the service item type. It might be simpler to grab all of these attributes and sort them out later during transformation steps in the daily job that loads the data. This is how the sample collect job is configured.


Each subscription represents a resource. In some cases, the service item type name serves as a resource name. In other cases, such as virtual machines, a specific resource based on the VM size or template is appropriate. The sample collection job captures each subscription as a single resource instance using the service item type as the resource name. The sample load job then modifies virtual machine resources by appending the size attribute so that each size has a specific money value associated. Another option is to break out CPU, memory and disk from VM attributes as individual resources for more precise costing.

Last modified


This page has no custom tags.


This page has no classifications.

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