Collecting data for additional instance type configuration metrics


The public cloud price catalogs are automatically updated in the product with each release or patch. The Migration Simulation Settings page displays the date when these customized price catalogs for all cloud providers were last updated in the product. For details, see Configuring the Migration Simulation settings

If you want to collect data for any additional instances that are not part of the catalog, you can define such instances along with configuration metrics in a JSON file. When you configure the ETL to use this JSON file and run it, the database is populated with these additional configuration metrics. If the same instance exists in the JSON file and catalog, the instance defined in the JSON file overrides the instance in the catalog. 

An out-of-the-box JSON file contains the mapping for configuration metrics collected by the extractor. You can configure this file to modify the existing instance type configuration or to add new configuration metrics. 

  1. Download the attached JSON file and update the file for existing and additional metrics.
    The following JSON file code shows some sample configuration metrics:

    {
    "instanceTypeConfiguration": {
    "standard_a10":{
       "REQUESTED_INSTANCE_TYPE": "Standard_A10",
           "CPU_MODEL":"Sparc",         
    "BYBENCHMARK_VALUE":{
                "SPECINT2006":"2006",    
    "SPECINT2008":"2008"
    }
    },
    "standard_a11":{
    "REQUESTED_INSTANCE_TYPE": "Standard_A11"
    }
    }
    }
  2. Name the JSON file appropriately, such as msazure-metric-conf.json, and save it to your local machine.
  3. Upload the file to a folder on the ETL Engine server.
  4. To use the file, include it when you create the ETL:
    1. In the Add ETL page, after you select Microsoft Azure - Azure extractor as the ETL, click Advanced and navigate to the Microsoft Azure configuration tab.
    2. Type the file path in Instance type definition JSON file path.
    3. Click Save.

For more information about configuring the ETL, see Microsoft Azure - Azure API Extractor.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*