PlateSpin has developed a robust Performance Data Import connector for PlateSpin Recon that allows users to import collected performance data from many third-party tools on the market into PlateSpin Recon to take advantage of its charting, reporting, and consolidation planning features.
When collected data has been moved from its proprietary location and format into a set of tables in the PlateSpin Recon monitoring database, PlateSpin Recon can import the data and make use of it like any other performance data. You can also set up a scheduled or recurring import, so the PlateSpin Recon analysis doesn’t have to be a one-time thing.
Almost all performance data gathering tools use a different method and format for storing the gathered data. To enable PlateSpin Recon to successfully import any data, regardless of its original format, you need to use an Extract, Transform, and Load (ETL) tool. This type of tool takes the data, reshapes it, and then loads it into the tables where PlateSpin Recon expects to find it. See Section 3.17.2, Preparing Data for Import into PlateSpin Recon.
The workloads in the data being imported need to be of the type that PlateSpin Recon can inventory under normal circumstances. All necessary ports between PlateSpin Recon and the workload being imported must be open.
As with other remote data connectors, data to be imported should contain one or more data points for every hour. Also, to use Consolidation Planning, specific counters need to exist in the data. See Section 3.15.1, Required Performance Counters.
There are four tables used for importing of generic performance data:
ImportComputer table: Contains information about computers that are to be imported into PlateSpin Recon.
ImportCounter table: Contains information about all counters that were collected for any of the computers in the ImportComputer table.
ImportCounterInstance table: Contains information about named instances of each counter for each computer. The combination of Computer, Counter and Instance Name must be unique.
ImportData table: Contains monitoring data to be imported.
Each table contains one ID field, which acts as a primary key and is automatically generated by the database server when a new row is inserted into the table.
Table 3-11 ImportComputer Table
Table 3-12 ImportCounter Table
Column Name |
Type |
Description |
---|---|---|
ID |
Integer |
Generated automatically. |
Name |
varchar(255) |
Unique name of the counter. This is the name of the counter as it will be shown in PlateSpin Recon charts. Some predefined counter names exist. See Section 3.15.1, Required Performance Counters. |
Table 3-13 ImportCounterInstance Table
Table 3-14 ImportData Table
To migrate data from a third-party location and format requires an Extract, Transform and Load (ETL) tool. There are many such tools on the market:
Open Source: CloverETL, Enhydra* Octopus, Pentaho* Data Integration, and Talend Open Studio.
You can also write proprietary data manipulation scripts, such as SQL queries, although the specifics of these tasks are beyond the scope of this document. For third-party tools, see the documentation that accompanies those tools. For scripts, refer to your in-house reference material on the languages and requirements.
Commercial: Informatica* PowerCenter*, Inaplex* Inaport*, and Altova* MapForce*.
Regardless of the tool you choose, the data transformation workflows are the same:
Retrieve hostnames of the workloads you want to import and write them to the ImportComputer table
Write the names of the required counters to the ImportCounter table
Retrieve and write all performance data related to the above counters
To work with generic imported data:
Collect data in the required performance and utilization measurement categories. See Section 3.15.1, Required Performance Counters.
Extract, transform, and load the collected performance data into the PlateSpin Recon Performance Data Import tables.
See Section 3.17, Using Performance Data Import to Import Generic Data into PlateSpin Recon, Section 3.17.1, Performance Data Import Tables Data Structure and Section 3.17.2, Preparing Data for Import into PlateSpin Recon.
Create a new Remote site for connecting to the Performance Data Import tables:
Right-click in the Data Center Explorer and select
.The Add Site dialog box is displayed.
Specify a
and, optionally, aClick the Remote from the list:
drop-down and selectFigure 3-21 Sample Performance Data Import Tables Remote Site Dialog Box
From the Performance Data Import
drop-down list, selectThe
check box is displayed.To empty the Performance Data Import tables of the data loaded in Step 2, select the check box.
If you choose not to allow PlateSpin Recon to empty these tables, you must do this manually before performing another import.
Click
The new site is added under
in the Data Center Explorer.Inventory the machines:
In the Data Center Explorer, right-click the remote site you just created and select
The Inventory Machines in Site
dialog box is displayed.Select the check boxes next to the machines you want to inventory.
Select the required credentials or select
to add new credentials.Click
Synchronize site data:
In the Data Center Explorer, right-click the required site and select
Select the check boxes next to the required machines. To select all machines in a site, select the check box next to the site.
Select required data range, scheduling, and recurrence options.
To perform a recurring import, you need to also set up a matching recurring Extract, Transform, and Load process to refresh the data in the PlateSpin Recon Performance Data Import tables. See your software vendor documentation for more details.
Click