The Data accordion includes a table that displays the column mappings defined in the Data Connector. Once the table is populated with the results of clicking the Run Request and Convert button, it also displays the results of running the Request.
You should not need to change any of the mappings settings for an Instance Collector based on a Data Connector unless you have changed details in the other accordions that affect the columns returned by the request (e.g., added a metric).
However, any changes you have made to the Template may affect the columns displayed in data table. New metrics need to be mapped, unwanted metrics need to be unmapped or unavailable metrics will be ignored.
Instance Collector mapping options:
-
Unused: Any column that is returned as part of the request but not used by the Template
-
Instance Identifier: this must be mapped to the column that includes the unique identifier of the instance that the Data Collector needs to include it its request to collect data for that instance from the RESTful API.
-
Instance Name: if the Instance identifier has an unreadable format then one or more columns can be used as the name Syncsort™ Capacity Management will use an Instance name. Each column is known as a component of the Instance name. The combination of all Instance name columns must be unique for each Instance. If no Instance name columns are mapped the Instance identifier column will be used as the Instance name.
For example, when collecting information about devices on a AWS machine if the AWS machine name and the device name are both mapped when reporting on the data every device for a single AWS machine can be can be selected automatically.
If you need to change the column mapping properties, see the online help for details.