An ETL module can be deployed in one or multiple instances (also called ETL tasks) in the same TrueSight Capacity Optimization implementation. For example, to extract data for different instances of the data source or to run multiple processes at the same time (related to different objects) from the same data source. Depending on the way an ETL has been implemented, an ETL task can be either a scheduled ETL, a process executed at scheduled time to run periodically against its data source, or a service ETL, a process that runs continuously.
A TrueSight Capacity Optimization administrator or user having the required privileges can deploy, execute and manage an ETL task. For more information about how to deploy, execute and manage an ETL task, see ETL tasks.
For information on how to develop custom ETL modules, see Developing custom ETLs.
Data is imported into TrueSight Capacity Optimization as time-series representing metrics for different types of entities. TrueSight Capacity Optimization provides three types of entities: systems, business drivers and domains.
In a TrueSight Capacity Optimization implementation, there can be more that one ETL module importing data for the same entities. For example, one ETL module might import performance data about servers, while a configuration management database (CMDB) ETL module might import asset numbers for the same servers. Unless specified, the default option in TrueSight Capacity Optimization considers all entities referred by ETL modules as distinct, therefore TrueSight Capacity Optimization provides a mechanism know as share lookup that allows you to configure two or more ETL modules to consider different entities referred by them as to represent the same entity. For more information, see Handling ETL lookup name.
For information about how TrueSight Capacity Optimization collects data using the ETL modules, see: