Use a CSV importer with tag values for the CI’s into Configuration Metrics, then using the tagging Rule to apply the Conf metric as a tag.
That’s how we did it in bulk.
I was able to use the csv importer for a config metric. But it only works for the agent created entity (virtual node) not the vCenter entity (virtual machine). So the two entities share the same name but from two ETL sources but the imported configuration item only associates with one. That is my issue.
You need to apply to each incoming ETL domain, because the SYSIDs are separate they are two separate entities in TSCO.
Can you give me an example of applying to a etl domain. No matter what I try I cannot get the configuration item applied to the vCenter entity.
to have two ETLs importing different metrics on the same entity, you have to make sure that the two systems are sharing the same lookup information. Entity name (the one visible in the workspace) is not considered during the lookup process. You can read more about lookup at the following BMC Documentation Page.
In your specific case:
- For Virtual Nodes, you are able to import the configuration metric since the "_COMPATIBILITY_" lookup field has the system name as value
- For Virtual Nodes, you are not able to import the configuration metric since the "_COMPATIBILITY_" lookup field has the VM UUID as value (I assume)
To import the configuration metric also at Virtual Machine level, you have two options:
- Modify the VMware vCenter ETL configuration to share the System Name as "_COMPATIBILITY_" (please make sure that this change does not have any other impact in your environment)
- Review your ETL design to make sure that the proper lookup fields/values are shared to reconcile entities. You can read more information regarding this last point at the following links
Thanks for the reply. Unfortunately I've read all of those pages and documents. But thinking further I am trying to import using the Generic CSV Columnar parser. Is that ETL only capable of the single lookup or can it use multiple lookups. The compatibility field has been changed for vCenter ETL and it is populated with system name. The issue is when running the ETL and it does the entity lookup the search finds the Virtual Node with the same name and not the Virtual machine. We are collecting data from the guests as well with the BMC agents. So it looks like i may need to use another ETL that can use multiple lookup
thanks for sharing more details with us.
As reported here (Custom ETL – Multiple Lookup) ), the "Generic ETL - CSV Columnar File Parser" only supports simple lookup. To use an horizontal format dataset (such as SYSCNF, you need to call a specific API to specify the lookup field.
In case of horizontal dataset, you need to call a specific API to specify the lookup field.
From this starting point, your best options are:
- Develop a Custom ETL in Integration Studio to enable the multiple lookup
- Using a multi-steps approach
- Load the content of the CSV in a Buffer Table (using the "Generic ETL - CSV Columnar File Parser" writing in a CST dataset)
- Create one or more Generic SQL Extractors for un-pivoting the content of the table and enabling multiple lookup (alternatively, using the ENTID#<sysid> macro)
In case, Moviri could absolutely help you with this activity. If interested, please feel free to shoot me an email at firstname.lastname@example.org
This is no longer true as BMC has updated the Generic ETL CSV Columnar File Parser to use multiple lookups with a recent patch.