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 Azure Services for Windows Server

Microsoft Azure Services for Windows Server

Table of contents
No headers

NOTE: This collector is deprecated in this release. To collect data about Azure private clouds, Cloud Cruiser recommends using the new Windows Azure Pack Collector. For more information, see Microsoft Windows Azure Pack.

Microsoft Azure Services for Windows Server retrieves usage data from multiple resource providers including System Center, websites, SQL Server, and MySQL Server. Cloud Cruiser can collect this data and then correlate it with collected subscription notifications to charge the usage to the correct customer. This solution involves two collectors.

This section contains the following articles:

To set up regular collection and loading of data

  1. Ensure that resources for Azure Services for Windows Server exist in Cloud Cruiser.
    These resources will be in the groups Azure Database , Azure Website , and Azure Virtual Machine . For more information, see Resources.
  2. Capture data for existing subscriptions and plans and configure Azure Services for Windows Server to provide future data.
    For more information, see Subscription and plan data.
  3. Ensure that you have the two provided Azure Services for Windows Server sample jobs saved as production jobs.
    If you selected the Microsoft Azure Services for Windows Server collector when installing Cloud Cruiser, the installer created the production jobs asfws_usage_download and asfws_daily_load for you. Otherwise you must save each sample job with a new name. For information about the sample jobs, see Sample jobs.
  4. Edit your usage collection job XML to set the usage time zone for the process and configure your data source, then run the job once.
    Running the job gives you JSON data to consult when you perform data mapping.
  5. Edit your load job XML to perform the following tasks:
    • Set the time zone for the process.
    • Set the timestamp formats and time zone required in your feed configurations. For more information, see Time and date.
    • Map the usage data you want to collect as identifiers and resources. For more information, see Data mapping.
    • Edit the process_subscriptions step so that it creates account identifiers that match your account structure, then edit the transform step to match.
    • Edit the extract_subscribers step to set the correct accountLength for your account identifiers.
    • Edit the aggregate step to perform the desired aggregation of resources.
    • Edit the transform step to perform the desired transformation of identifiers and resources.
  6. Run the load job.
    This not only gives you a chance to debug your XML, it also loads Azure Services for Windows Server rate plans into Cloud Cruiser.
  7. For each resource for which you will charge, set the desired rate.
    If you want to charge for a resource at multiple rates, clone it to the appropriate Azure Services for Windows Server rate plans. For more information, see Setting alternative rates with rate plans.
  8. Schedule both jobs to run daily, with the load job starting thirty minutes after the collection job.
Last modified

Tags

This page has no custom tags.

Classifications

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