Generic - Columnar database extractor
This topic describes how to import generic data using the Columnar SQL Extractor.
This topic contains the following sections:
Integration steps
To integrate TrueSight Capacity Optimization with the CSV columnar database extractor, perform the following task:
- Navigate to Administration > ETL & SYSTEM TASKS > ETL tasks.
- In the ETL tasks page, click Add > Add ETL under the Last run tab.
In the Add ETL page, set values for the following properties under each expandable tab.
Basic properties
Advanced properties
- Click Save.
You return to the Last run tab under the ETL tasks page. - Validate the results in simulation mode: In the ETL tasks table under ETL tasks > Last run, locate your ETL (ETL task name), click
to run the ETL.
After you run the ETL, the Last exit column in the ETL tasks table will display one of the following values:- OK: The ETL executed without any error in simulation mode.
- WARNING: The ETL execution returned some warnings in simulation mode. Check the ETL log.
- ERROR: The ETL execution returned errors and was unsuccessful. Edit the active Run configuration and try again.
- Switch the ETL to production mode: To do this, perform the following task:
- In the ETL tasks table under ETL tasks > Last run, click the ETL under the Name column.
- In the Run configurations table in the ETL details page, click
to edit the active run configuration.
- In the Edit runconfigurationpage, navigate to the Run configuration expandable tab and set Execute in simulation mode to No.
- Click Save.
- Locate the ETL in the ETL tasks table and click
to Run it, or schedule an ETL run.
After you run theETL, or schedule the ETL for a run, it will extract thedataform the source and transfer it to the TrueSight Capacity Optimization database.
Configuring the ETL
Below is an example query that can be used to extract generic data. It can be used as a template to create custom extraction queries:
from my_table d and d.ts > ?
You can use the :PARL placeholder parameter one or multiple times in a query; it is replaced by the last saved lastcounter value.
SELECT d.ts as TS, d.interval as DURATION, d.id as DS_SYSNM, d.name as SYSNM, d.fsname as SUBOBJNM, d.avgvalue as BYFS_FREE, d.size as BYFS_SIZE
from my_table d and d.ts > :PARL
#Example 2
SELECT d.ts as TS, d.ats as ACTIVITYDATE, d.interval as DURATION, d.id as DS_SYSNM, d.name as SYSNM, d.fsname as SUBOBJNM, d.avgvalue as BYFS_FREE, d.size as BYFS_SIZE from my_table d and d.ts > :PARL OR d.ats > :PARL
To import system metrics, configure the SYSDAT dataset to import system metrics. The 'TS' column is used as last counter. You can configure the default last counter in Advanced mode; if not configured, the default is 7 days from the ETL start date.
To import business driver data, configure the WKLDAT dataset as shown below:
from my_table d and d.ts > ?
Supported datasets
This ETL supports vertical datasets: SYSDAT , WKLDAT .
Metric filtering is performed within the extraction query. Only one dataset per extraction is supported.
Related topics
Dataset-reference-for-ETL-tasks
Horizontal and Vertical datasets
Viewing-datasets-and-metrics-by-dataset-and-ETL-module
Determining-how-to-aggregate-data-to-a-given-resolution-using-SQL