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 > Microsoft Azure > Creating Microsoft Azure collections

Creating Microsoft Azure collections

HPE Consumption Analytics Portal includes several collectors that enable you to collect a variety of Microsoft Azure data. This topic provides information about the prerequisites for using the Microsoft Azure collectors, and details any collector-specific properties available. For a general procedure for creating collections, see Creating collections.

Understanding when to use each collector

Each of the Azure collectors in HPE Consumption Analytics Portal serves a particular purpose. Understanding what each collector is designed to do can help you build the right set of collections for your Azure environment. The following table lists the Azure account type supported by each collector, and provides information about why you would want to use each collector. It also lists the HPE Consumption Analytics Portal data source and Azure APIs used by each collector.

Collector Azure account type Use cases and notes Data source Azure API
Azure EA Billing Enterprise Agreement Use this collector to retrieve resource usage and billing data.

This collector also retrieves tags created in the Azure Preview portal. If you want to collect tags from the Classic Azure portal, supplement your collections with an Azure Tags collection.

If you want to collect diagnostics data for your VMs, supplement your collections with an Azure Metrics collection.

Microsoft Azure EA Billing Billing and Usage
Azure Metrics

Subscription

Use this collector to retrieve Azure VM diagnostics data, including CPU utilization and network traffic.

Metrics are collected only for VMs with Diagnostics enabled in Azure.

Microsoft Azure Insights
Azure Rate Card Subscription If you do not have a Microsoft Enterprise Agreement, use this collector to retrieve Azure services and their rates.

You can use this collector in conjunction with the Azure Usage collector to retrieve the same type of information you would get with the Azure EA Billing collector.

Microsoft Azure RateCard
Azure Tags Subscription Use this collector to retrieve tag metadata for your Azure resources, which can help you identify resource owners, regions, and cost centers. Microsoft Azure

Azure Resource Manager (ARM)

Azure Usage Subscription If you do not have a Microsoft Enterprise Agreement, use this collector to retrieve consumption information for Azure resources.

You can use this collector in conjunction with the Azure Rate Card collector to retrieve the same type of information you would get with the Azure EA Billing collector.

Microsoft Azure Usage

For more information about creating Azure data sources to support these collectors, see Creating Microsoft Azure data sources.

The Azure resource data available to collect can depend upon the deployment model (Classic or ARM) used to deploy those resources. For example:

  • For resources created in the Classic deployment model, Azure aggregates usage data at the resource group level. For resources created in the ARM deployment model, you can collect usage data for individual resources.
  • Tags are available at the resource group level in Classic deployments, and for individual resources in ARM deployments.
  • For resources created in classic deployments, the resource.id dimension for the Microsoft Azure Tags collector shows the resource name only (such as boomlet). For resources created in ARM deployments, the resource.id dimension shows the full path for that resource (such as /subscriptions/<id>/resourceGroups/alphabetsoupCC/providers/Microsoft.Compute/virtualMachines/boomlet).

Microsoft Azure EA Billing collector

The Microsoft Azure EA Billing collector retrieves usage and cost data from the Azure Usage Report through the Azure Billing and Usage API. This collector supports only Azure accounts linked to an Enterprise Agreement. Before you begin you must already have a Microsoft Azure Enterprise Agreement account set up. If your Azure account is not linked to an Enterprise Agreement, you must use using other Azure collectors to retrieve your Azure data.

The collector named Microsoft Azure in previous versions of HPE Consumption Analytics Portal has been renamed Microsoft Azure EA Billing in version 4.2.10. The renamed collector functions exactly as it did in previous versions. The only change is its name.

On the Microsoft Azure EA Billing Properties section of the Edit Collection dialog box, you can configure the following properties:

Property Description
Lines to Skip

Instructs HPE Consumption Analytics Portal to skip the specified number of lines in the imported data. Use this property to keep data unrelated to usage and billing out of HPE Consumption Analytics Portal. The default is 2.

To determine how many lines you should skip, see the Input Data section in the Advanced Configuration dialog box.

Includes Header Row

Informs HPE Consumption Analytics Portal whether the first row of retrieved data should be treated as header information rather than usage or billing information. The default is Yes.

To determine whether collected data contains information you can use as headers, see the Input Data section in the Advanced Configuration dialog box.

API version The Microsoft Azure API version you are using, either 1.0 (the default) or 2.0. Microsoft recommends that you use version 1.0.

eabillingProperties.png

This collector works with the Microsoft Azure EA Billing data source. For more information, see Creating Microsoft Azure data sources.

Microsoft Azure Metrics collector

The Microsoft Azure Metrics collector enables you to collect diagnostics data for VMs with diagnostics enabled in Microsoft Azure through the Metrics portion of the Azure Insights API. Diagnostics captures system data on the virtual machines and virtual machine instances that run your cloud service. You can use this data for debugging and troubleshooting, measuring performance, monitoring resource usage, traffic analysis and capacity planning, and auditing.

This collector retrieves information about CPU utilization, incoming network bytes, and outgoing network bytes through the Azure Insights API. For detailed information, see Dimensions and measures collected from Microsoft Azure.

This collector works with the Microsoft Azure data source. For more information, see Creating Microsoft Azure data sources.

Before using the Microsoft Azure Metrics collector, you must first ensure that one or more Azure VMs have diagnostics enabled. The Microsoft Azure Metrics collector retrieves data only for VMs with diagnostics enabled.

To enable diagnostics for an Azure VM

  1. In the Azure Preview portal (https://portal.azure.com) click Virtual Machines.
  2. Click the VM you want to modify.
  3. In the Monitoring area of the menu pane, click Diagnostics settings.
  4. In the Diagnostics pane, select the Basic metrics box, and then set the Status field to On.
    enableDiagnostics.png
  5. Click Save.
  6. Repeat this procedure as needed to enable diagnostics for other VMs.

Microsoft Azure Rate Card collector

The Microsoft Azure Rate Card collector retrieves services and rates from Microsoft Azure through the Azure RateCard API. This functionality enables you to publish your Azure services and rates to HPE Consumption Analytics Portal, associate Azure resource usage to the collected services, and charge per the collected rates.

When creating a Microsoft Azure Rate Card collection, you must specify the following properties on the Microsoft Azure Rate Card Properties section of the Edit Collection dialog box:

Property Description
Offer The Offer ID of the Azure subscription you want to collect. You can find this on the Subscription Summary page in the Classic Azure portal.
Currency The code for the currency used to price services in Azure. (for example, USD). You can find this on the Subscription Summary page in the Classic Azure portal.
Locale The abbreviation for the culture for which the resource metadata is localized in Azure (for example, en-US). For a list of locale strings, see http://www.science.co.il/language/locale-codes.asp.
Region The 2-letter ISO code for the country in which the Azure offer was purchased (for example, US). For a list of region codes, see https://en.wikipedia.org/wiki/ISO_3166-2.

ratecardProperties.png

In your workbook, consider using transformation steps to remove services you do not need. For example, you might be interested in billing for Infrastruture-as-a-service resources only. When you have transformed the data as needed, use a Publish as Service and Rates workflow step to map your Azure services and rates to HPE Consumption Analytics Portal. For more information, see Import services and rate plans.

This collector works with the Microsoft Azure data source. For more information, see Creating Microsoft Azure data sources.

Microsoft Azure Tags collector

The Microsoft Azure Tags collector enables you to collect tags defined for your Microsoft Azure resources. For example, you might tag resources to identify their owners, regions, and cost centers. Consider using this collector in conjunction with other Microsoft Azure collector to help you identify and sort Azure resources in HPE Consumption Analytics Portal.

On the Microsoft Azure Tags Properties section of the Edit Collection dialog box, you can configure the following properties:

Property Description
Show Resource Tags Determines whether HPE Consumption Analytics Portal will collect tags defined at the resource level. The default is Yes.
Resource Tags Prefix A text string you want to prepend to your resource tags. For example, if you enter resource-, all resource tag columns are collected as resource-<tag>.
Show Resource Group Tags Determines whether HPE Consumption Analytics Portal will collect tags defined at the group level. The default is Yes.
Resource Group Prefix A text string you want to prepend to your group tags. For example, if you enter group-, all group tag columns are collected as group-<tag>.
Include Untagged Resources Determines whether HPE Consumption Analytics Portal will collect resources that have no tags. The default is No.
Tag Conflict Resolution Determines how to resolve a conflict in tagging when a resource has the same tag defined at the resource and group levels. The default is RESOURCES_OVERRIDE_GROUPS.

tagsProperties.png

This collector works with the Microsoft Azure data source. For more information, see Creating Microsoft Azure data sources.

Microsoft Azure Usage collector

The Microsoft Azure Usage collector enables you to collect consumption information (in terms of meter quantities) for your Microsoft Azure VM infrastructure, through Microsoft's Azure Usage API. By understanding how your Azure resources are being consumed in your organization, you can make more informed decisions about where and by how much you need to increase or decrease your cloud investment.

On the Microsoft Azure Usage Properties section of the Edit Collection dialog box, you can choose whether you want to collect either Daily or Hourly aggregated data.

usageProperties.png

Last modified

Tags

Classifications

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