Troubleshooting issues with the migration of configuration metrics

When you migrate data from TrueSight Capacity Optimization to BMC Helix Continuous Optimization by using the migration toolkit provided in version 24.4.01 or later, data for some of the configuration metrics created in TrueSight Capacity Optimization might not be imported to BMC Helix Continuous Optimization. This issue causes a data validation discrepancy between the TrueSight and Helix environments. Perform the troubleshooting steps provided in this topic to import the missing data to BMC Helix Continuous Optimization for effective and accurate visibility into capacity planning. 

Related topics

Running-the-migration-tool

Migrating-to-BMC-Helix-Continuous-Optimization

Issue symptoms

Some of the imported entities do not show the configuration metrics.

Issue scope

This issue occurs after migrating data from TrueSight Capacity Optimization to BMC Helix Continuous Optimization.


Resolution

Perform the following steps to migrate the configuration metrics again: 

  1. Modify the run configuration of the data migrator ETL. 
    1. Log in to BMC Helix Continuous Optimization.
    2. Select Administration > ETL & System tasks > ETL tasks.
    3. On the ETL tasks page, click the name of the data migrator ETL.
    4. In the Run configurations table, click Edit this run configuration edit_simulation_icon.png.
    5. On the Run configuration tab, click the You can manually edit ETL properties from this page link. 
    6. In the Add new property field at the bottom of the page, type the name of the property as import.conf.metrics and click Add. 
    7. Locate the new property in the list of properties, type the value as true, and click Save.
      migration_conf_prop.png


  2. Click Run active configuration to re-run the data migrator ETL.
    After this data migrator ETL task completes the first run, you can see the reimported configuration data.
  3. Verify the ETL run and imported data.
    1. To verify whether the ETL ran successfully:
      1. On the data migrator ETL details page, review the Run History table. 
      2. In the Last exit column, verify that the status is OK.
      3. In the # loaded entities column, verify that the entities are loaded in each run. 
    2. To verify that the missing configuration metrics data is imported: 
      1. In the left pane of the Workspace tab, expand the relevant domain name for which you noticed the missing configuration data earlier: for example, Virtual Machine - VMware.   
      2. Click the entity and select the Metrics tab. 
      3. Verify the configuration metrics values in the table.


Warning

After successfully importing all the configuration metrics, disable the migration of configuration metrics by setting import.conf.metrics to false. This will help avoid any impact on ETL performance. 

 

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