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 3 > Setting Up Collection > Native collectors > Microsoft Windows Azure Pack > Feed configuration

Feed configuration

Table of contents

The following considerations apply to the feed configurations in the load job.

Data mapping

All Windows Azure Pack services are mapped to resources in the default load job, so you should only modify the data mapping if you want to use different resource names for these services or do not want to charge for some of them.

Because Cloud Cruiser uses the JSON Collector to collect Windows Azure Pack data, you map this data the same way as other data collected by the JSON Collector. You can map common attributes at the root level but will need to use JSONPath expressions for nested attributes specific to each resource provider type. For information about mapping for the JSON Collector, see Data mapping.

To see what elements and attributes are available to map, examine the JSON files in the subdirectories of <working_dir>/usage_files/azure_pack/usage after running the collection job.

Timestamps

You must use different dateTimePattern values for the usage feed and the event feeds, as shown in the sample load job. For more information, see Time and date.

Last modified

Tags

This page has no custom tags.

Classifications

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