Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Azure > Flows in the Microsoft Azure templates

Flows in the Microsoft Azure templates

Cloud Cruiser includes two workbook templates for Microsoft Azure: The Microsoft Azure template (used for CloudSmart-Now solutions) and the Microsoft Azure Tags template (which includes additional workflow to collect tag data).

Microsoft Azure template

The Microsoft Azure workbook template includes several flows that consolidate subscription, usage, and resource ownership information to a simple format that allows you to understand how to charge for the actual usage of specific Microsoft Azure services. This template is used in the CloudSmart-Now solution for Microsoft Azure.

For detailed information about the raw data collected from Microsoft Azure, see Dimensions and measures collected from Microsoft Azure.

Flow Description
Ownership imports resource-ownership data from the ResourceOwnership collection, and then creates lookup files that are used by later flows to associate owners and departments to specific resources. This flow is useful when you are not using fields in the Azure billing data to associate departments and owners with resources.
ImportServices Collects raw Microsoft Azure usage data from the Azure1 collection, and then normalizes the unique measure names for each service to a common name (ResourceQtyConsumed). This consolidates the measurement columns for various Azure services to a single column, making it easier to read Cost and Rate usage data in Cloud Cruiser. To ensure that it keeps only the data that is relevant and useful, the flow deletes all dimensions except for Product, ServiceInfo, and ServiceResource, and deletes all measures that have a value of 0. The flow then aggregates the transformed data and publishes it to your Cloud Cruiser database
PublishData

Collects raw Microsoft Azure usage data from the Azure1 collection, and normalizes the unique measure names for each service to a common name (ResourceQtyConsumed). It then determines whether it should retrieve owner and department information from Microsoft Azure data or from data you entered in the ResourceOwnership.csv file, based on the the value of the UseOwnershipFile workbook parameter. If it uses the file, the flow obtains owner and department information from the lookup files created by the Ownership flow. If the flow cannot locate an owner or department, it sets the related Owner or Department dimension to Unknown.

The flow also calculates VM sizing data for Virtual Machine records, and then compares that data to standard VM sizes defined in the lookup tables you imported. For VMs that fall outside of the definitions in the lookup table, the flow marks those records as nonstandard. For more information, see VM sizing guidelines for CloudSmart-Now.

Lastly, the flow deletes unnecessary dimensions, and publishes the data to the Cloud Cruiser database.

HandleNonStandard Imports non-standard VMs identified by the PublishData step, and then removes all measures, and dimensions other than VMType, ResourceID, Owner, and Department.  For every non-standard VM, the flow generates an exception message visible in the Data > Processing > Monitoring area of Cloud Cruiser.
ImportCustomers Imports data from the PublishData dataset, and then removes all measures, and all dimensions other than Owner and Department. It aggregates and publishes Owner data, and the aggregates and publishes Department data.
HandleUnknowns Alerts you about any resources that do not have assigned owners and departments. It begins by importing data from the PublishData dataset, removing all measures, and removing all dimensions except for ResourceGUID, Owner, and Department. The flow then scans the Owner and Department fields for a value of Unknown. For every Unknown value, the flow generates an exception message visible in the Data > Processing > Monitoring area of Cloud Cruiser.

Microsoft Azure Tags template

The Microsoft Azure Tags template was deprecated in Cloud Cruiser 4.2.10. To collect Microsoft Azure tags, use the Microsoft Azure Tags collection with the Microsoft Azure data source introduced in Cloud Cruiser 4.2.10. For more information, see Creating Microsoft Azure data sources and Creating Microsoft Azure collections.

The Microsoft Azure Tags workbook template includes two flows that collect raw service and usage data from Microsoft Azure, and then transform and publish the data in Cloud Cruiser. The template includes two additional flows to collect and process tag information.

For detailed information about the raw data collected from Microsoft Azure, see Dimensions and measures collected from Microsoft Azure.

Flow Description
ImportServices Collects raw Microsoft Azure service data into Cloud Cruiser. As part of its transformation process the flow renames the Product dimension to ComputedServiceName, which is later used in Cloud Cruiser to list he name of each service. The flow also deletes all unnecessary dimensions, and all measures. The purpose of this flow is to transform and publish collected service data, so measures are not needed as part of this flow. Measurement data is processed in the PublishData flow, described below. The flow aggregates matching rows of data to speed processing and reduce storage needs for the transformed data in your Cloud Cruiser database, and then publishes service names to Cloud Cruiser.
PublishData Collects raw Microsoft Azure usage data into Cloud Cruiser, and then normalizes the unique measure names for each service to a common name (ResourceQtyConsumed). This consolidates the various measurement columns for various Azure services to a single column, making it easier to read Cost and Rate usage data in Cloud Cruiser. The flow then publishes the transformed usage data to your Cloud Cruiser database, allowing you to understand how to charge for the actual usage of the services collected by the ImportServices flow.
ClassicTags Imports resource tags from the collection named apc_tags_group_collection. By default, the flow removes hidden tags, though you can disable the processor that hides those tags. The flow removes unnecessary dimensions, and then renames dimensions to show ResourceGroup andSubscriptionGuid data. Lastly, the flow aggregates tag data.
ModernTags Imports resource and group tags from the collection named apc_tags_both_collection. By default, the flow shows hidden tags, though you can enable a processor that removes hidden tags. The flow removes unnecessary dimensions, and then renames dimensions to show ResourceGroup and Instance Id data.
Last modified

Tags

Classifications

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