BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 Generic view extractor

Use the BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 Generic view extractor to collect the PATROL metrics data from the ProactiveNet Performance Management Sybase database. This is an open extractor tool and you can use it to load data collected by a PATROL Knowledge Module.

Collecting data by using the BMC TrueSight Operations Management Generic ETL

To collect data by using the BMC TrueSight Operations Management Generic ETL, do the following tasks:

I. Complete the preconfiguration tasks.

II. Configure the ETL.

Step I. Complete the preconfiguration tasks

Configure the ETL in TrueSight Capacity Optimizationset up the connection with the BMC ProactiveNet repository database, using one of the following account configurations:

    • For Sybase database: dba account
      To set up the connection to the Sybase database: On your TrueSight Capacity Optimization ETL engine server, edit the file /opt/cpit/etl/freetds/etc/freetds.conf to configure the connectivity to your BMC ProactiveNet Sybase database.

      Example
      [BPPMSYBASESERV]
          host=<your_server_ip>
          port = 2638
          tds version=5.0
      
    • For Oracle database: proact account or any user having access to the BMC ProactiveNet database schema

      To set up the connection to an Oracle database using Perl ETLs, you can either edit the tnsnames.ora file using the oracle user, or manually specify the host details in the Database TNS name field of the configuration panel.

      • Configuring by editing the TNSNAMES.ORA file

        On your ETL engine server, from the installation directory of the Oracle client, edit the file $ORACLE_CLIENT_HOME/network/admin/tnsnames.ora to configure the connectivity to your database. Ensure that you have write permissions on this file.

        Example
        DB=
        (
         DESCRIPTION=
          (ADDRESS=
            (PROTOCOL=TCP)
            (HOST=<your_server_ip>)
            (PORT=<port>)
          )
          (CONNECT_DATA=
            (SERVER=default)
            (SERVICE_NAME=<service_name>)
          )
        )
         Testing the Oracle connection from the command line

        Execute the following commands as TrueSight Capacity Optimization OS user:

        . $CPITBASE/env.sh
        sqlplus user/password@DB

        $CPITBASE is the TrueSight Capacity Optimization installation path — for example{{/opt/cpit}}.

        To troubleshoot the database connection, verify that you can:

        • Reach your database server from the ETL engine machine by running the command ping <your_db_server_ip>
        • Remotely access your database server using telnet from the ETL engine machine, by running the command telnet<your_db_server_ip> <your_db_server_port>
        • Connect to your database using a software client, specifying the same credentials
      • Configuring without editing the TNSNAMES.ORA file

        If you do not have the required permissions to edit tnsnames.ora, you can set up the connection to an Oracle database specifying the host details in the Database TNS name field of the configuration screen:

        host=<database_host>;sid=<DBSID>;port=1521

Step II. Configure the ETL

You must configure the ETL to connect to TrueSight Operations Management for data collection. ETL configuration includes specifying the basic and optional advanced properties. While configuring the basic properties is sufficient, you can optionally configure the advanced properties for additional customization.

A. Configuring the basic properties

Some of the basic properties display default values. You can modify these values if required.

To configure the basic properties:

  1. In the TrueSight Capacity Optimization console, navigate to Administration ETL & System Tasks > and select ETL tasks.
  2. On the ETL tasks page, click Add > Add ETL under the Last run tab. The Add ETL page displays the configuration properties. You must configure properties in the following tabs: Run configuration, Entity catalog, SQL query, and Connection parameters.
  3. On the Run configuration tab, select BMC - TrueSight Operations Management 9.0/9.5/9.6/10.0 Generic view extractor. The name of the ETL is displayed in the ETL task name field. You can edit this field to customize the name.
  4.  Click the Entity catalog tab, and select one of the following options:

    • Shared Entity Catalog: Select if the other ETLs access the same entities that are used by this ETL.

      • From the Sharing with Entity Catalog list, select an entity catalog name that is shared between ETLs.
    • Private Entity Catalog: Select if you want to use this ETL independently.
  5. On the SQL query tab, build the SQL extraction query. Specify the SQL extraction query. You can select the required parameter and operator from the list and add them to the text area. This tab is only available when a custom database query has to be built in order to get the data from a generic source. The form allows you to configure the following properties. A text area in which you can type the SQL extraction query.

     Fields you can use on the query, query format, and example
    You can format the query according to the following structure:
    SELECT scfg.{ENTNM_FIELD} as SYSNM,
           scfg.{ENTNM_FIELD} as DS_SYSNM,
           [ss.{SUBENTNM_FIELD} as SUBOBJNM,]
           [ss.{SUBENTNM_FIELD} as DS_SUBOBJNM,]
           (ss.TIMERECORDED - mod(ss.TIMERECORDED,<<RESO>>) as TS,
           AVG(ss.{FIELD}) AS {BCO_METRIC}
    FROM   {CONFIG_VIEW} scfg JOIN
    	     {ST_VIEW} ss  ON ss.MOINSTID=scfg.MOINSTID
    WHERE  convert(datetime, ctime(ss.TIMERECORDED)) > ?
    			 [{OTHER_WHERE_CONDITIONS}]
    GROUP BY DS_SYSNM, SYSNM, TS
    ORDER BY DS_SYSNM, SYSNM, TS ASC
    

    Example: This example extracts DISK_TRANSFER_RATE and DISK_IO_RATE from an Oracle database for the Microsoft Windows NT platform:

    SELECT lower(scfg.DEVICENAME) as SYSNM,
           lower(scfg.DEVICENAME) as DS_SYSNM,
           ss.TIMERECORDED - mod(ss.TIMERECORDED,<<RESO>>) as TS,
           AVG((SS.READSEC + SS.WRITESEC)/1024) AS DISK_TRANSFER_RATE,
           AVG(AVGDISKTRAN) as DISK_IO_RATE,
    FROM   NTDISKPERF_CFG_VIEW scfg JOIN
    	     NTDISKPERF_ST_VIEW ss  ON ss.MOINSTID=scfg.MOINSTID
    WHERE  to_date(ss.TIMERECORDED,'YYYY-MM-DD HH24:Mi:SS') > ?
    			 AND SCFG.INSTNAME = '_Total'
    			 AND SS.READSEC >= 0 and SS.WRITESEC >= 0
    GROUP BY DS_SYSNM, SYSNM, TS
    ORDER BY DS_SYSNM, SYSNM, TS ASC
    
     Available and mandatory fields that can be used in the query:

    Field name

    Mandatory

    Description

    Default

    SYSNM

    Yes

    System name

    DS_SYSNM

    Yes

    System name as reported by data source (used for lookup)

    SUBOBJNM

    No

    Subobject identifier

    GLOBAL

    DS_SUBOBJNM

    No

    Subobject identifier as reported by data source

    GLOBAL

    TS

    Yes

    Timestamp as reported by data source

    Note: The <<RESO>> (or :RESO) macro must be inserted in the query structure in order to floor data source timestamps. Aggregation resolution (set to 1 hour as default) can be changed in the General configuration tab (Advanced Mode) and will be used as sample duration.

    SYSTYPENM

    No

    BMC TrueSight Capacity Optimization System type


  6. Click the Connection parameters tab, and configure the following properties:

    PropertyDescription
    Datasource typeSelect one of the following options:
    • Select existing datasource
      • Datasource: From the Datasource list, select a datasource.
    • Custom datasource:
      • Database type: Select a database type from the drop down list. 

      • Database user: Type the user name to connect to the database.

      • Database password: Type the user name to connect to the database.

      • Data source name (Applicable to Microsoft SQL Server/Sybase): Type in the data source name.

      • Database name (Applicable to Microsoft SQL Server/Sybase): Type in the database name.

      • Database TNS name (Applicable to Oracle): Type in the Database TNS name.

      • Connection URL (Applicable to Other database): Enter the connection URL.


    The following image shows the basic properties configuration.

  7. (Optional) Override the default values of properties in the following tabs:

     Run configuration
    PropertyDescription
    Module selection

    Select one of the following options:

    • Based on datasource: This is the default selection.
    • Based on Open ETL template: Select only if you want to collect data that is not supported by TrueSight Capacity Optimization.
    Module descriptionA short description of the ETL module.
    Execute in simulation modeBy default, the ETL execution in simulation mode is selected to validate connectivity with the data source, and to ensure that the ETL does not have any configuration issues. In the simulation mode, the ETL does not load data into the database. This option is useful when you want to test a new ETL task. To run the ETL in the production mode, select No.
    BMC recommends that you run the ETL in the simulation mode after ETL configuration and then run it in the production mode.
    Datasets

    Specify the datasets that you want to add to the ETL run configuration. The ETL collects data of metrics that are associated with these datasets.

    1. Click Edit.
    2. Select one (click) or more (shift+click) datasets from the Available datasets list and click >> to move them to the Selected datasets list.
    3. Click Apply.

    The ETL collects data of metrics associated with the datasets that are available in the Selected datasets list.

     Object relationships
    PropertyDescription
    After import

    Specify the domain where you want to add the entities created by the ETL. You can select an existing domain or
    create a new one.

    Select one of the following options:

    • leave all new entities in 'Newly Discovered': This option is selected by default.

    • move all new entities in a new Domain.
      • New domain: Select a parent domain, and specify a name for your new domain.
    • move all new entities in an existing Domain: Select an existing domain from the Domain list. If the selected domain is already used by other hierarchy rules, select one of the following Domain conflict options:
      • Enrich domain tree: Select to create a new independent hierarchy rule for adding a new set of entities, relations, or both that are not defined by other ETLs.
      • ETL Migration: Select if the new ETL uses the same set of entities, relations, or both that are already defined by other ETLs.

     ETL task properties
    PropertyDescription
    Task groupSelect a task group to classify the ETL.
    Running on schedulerSelect one of the following schedulers for running the ETL:
    • Primary Scheduler: Runs on the Application Server.
    • Generic Scheduler: Runs on a separate computer.
    • Remote: Runs on remote computers.
    Maximum execution time before warningIndicates the number of hours, minutes, or days for which the ETL must run before generating warnings or alerts, if any.
    Frequency

    Select one of the following frequencies to run the ETL:

    • Predefined: This is the default selection. Select a daily, weekly, or monthly frequency, and then select a time to start the ETL run accordingly.
      • Start timestamp: hour\minute: Select the HH:MM start timestamp to add to the ETL execution running on a Predefined frequency.
    • Custom: Specify a custom frequency, select an appropriate unit of time, and then specify a day and a time to start the ETL run.
      • Custom start timestamp: Select a YYYY-MM-DD HH:MM timestamp to add to the ETL execution running on a Custom frequency.

  8. Click Save.
    The ETL tasks page shows the details of the newly configured BMC TrueSight Operations Management ETL.

(Optional) B. Configuring the advanced properties

You can configure the advanced properties to change the way the ETL works.

To configure the advanced properties:

  1. On the Add ETL page, click Advanced.
  2. Configure the following properties:

     Run configuration
    PropertyDescription
    Run configuration nameSpecify the name that you want to assign to this ETL task configuration. The default configuration name is displayed. You can use this name to differentiate between the run configuration settings of ETL tasks.
    Deploy statusSelect the deploy status for the ETL task. For example, you can initially select Test and change it to Production after verifying that the ETL run results are as expected.
    Log levelSpecify the level of details that you want to include in the ETL log file. Select one of the following options:
    • 1 - Light: Select to add the bare minimum activity logs to the log file.
    • 5 - Medium: Select to add the medium-detailed activity logs to the log file.
    • 10 - Verbose: Select to add detailed activity logs to the log file.

    Use log level 5 as a general practice. You can select log level 10 for debugging and troubleshooting purposes.

    Datasets

    Specify the datasets that you want to add to the ETL run configuration. The ETL collects data of metrics that are associated with these datasets.

    1. Click Edit.
    2. Select one (click) or more (shift+click) datasets from the Available datasets list and click >> to move them to the Selected datasets list.
    3. Click Apply.

    The ETL collects data of metrics associated with the datasets that are available in the Selected datasets list.

    Default last counter

    Set the default timestamp (dd/mm/yyyy hh:mm:ss) to use when the ETL executed for the first time.

    Extract resolutionSpecify a value so that data will be aggregated into samples with the specified granularity.

     Collection level
    PropertyDescription
    Metric profile selection

    Select the metric profile that the ETL must use. The ETL collects data for the group of metrics that is defined by the selected metric profile.

    • Use Global metric profile: This is selected by default. All the out-of-the-box ETLs use this profile.
    • Select a custom metric profile: Select the custom profile that you want to use from the Custom metric profile list. This list displays all the custom profiles that you have created.

    For more information about metric profiles, see Adding and managing metric profiles.

    Levels up to

    Specify the metric level that defines the number of metrics that can be imported into the database. The load on the database increases or decreases depending on the selected metric level.To learn more about metric levels, see Aging Class mapping.

     Additional properties
    PropertyDescription
    List of properties

    Specify additional properties for the ETL that act as user inputs during run. You can specify these values now or you can do so later by accessing the "You can manually edit ETL properties from this page" link that is displayed for the ETL in the view mode.

    1. Click Add.
    2. In the etl.additional.prop.n field, specify an additional property.
    3. Click Apply.
      Repeat this task to add more properties.

     Loader configuration
    PropertyDescription
    Empty dataset behaviorSpecify the action for the loader if it encounters an empty dataset:
    • Warn: Generate a warning about loading an empty dataset.
    • Ignore: Ignore the empty dataset and continue parsing.
    ETL log file nameThe name of the file that contains the ETL run log. The default value is: %BASE/log/%AYEAR%AMONTH%ADAY%AHOUR%MINUTE%TASKID
    Maximum number of rows for CSV outputA numeric value to limit the size of the output files.
    CSV loader output file nameThe name of the file that is generated by the CSV loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
    Capacity Optimization loader output file nameThe name of the file that is generated by the TrueSight Capacity Optimization loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
    Detail mode
    Specify whether you want to collect raw data in addition to the standard data. Select one of the following options:
    • Standard: Data will be stored in the database in different tables at the following time granularities: Detail (configurable, by default: 5 minutes), Hourly, Daily, and Monthly.
    • Raw also: Data will be stored in the database in different tables at the following time granularities: Raw (as available from the original data source), Detail (configurable, by default: 5 minutes), Hourly, Daily, and Monthly.
    • Raw only: Data will be stored in the database in a table only at Raw granularity (as available from the original data source).

    For more information, see Accessing data using public views and Sizing and scalability considerations.

    Remove domain suffix from datasource name (Only for systems) Select True to remove the domain from the data source name. For example, server.domain.com will be saved as server. The default selection is False.
    Leave domain suffix to system name (Only for systems)Select True to keep the domain in the system name. For example: server.domain.com will be saved as is. The default selection is False.
    Update grouping object definition (Only for systems)Select True if you want the ETL to update the grouping object definition for a metric that is loaded by the ETL. The default selection is False.
    Skip entity creation (Only for ETL tasks sharing lookup with other tasks)Select True if you do not want this ETL to create an entity and discard data from its data source for entities not found in Capacity Optimization. It uses one of the other ETLs that share a lookup to create a new entity. The default selection is False.

     Scheduling options
    PropertyDescription
    Hour maskSpecify a value to run the task only during particular hours within a day. For example, 0 – 23 or 1, 3, 5 – 12.
    Day of week maskSelect the days so that the task can be run only on the selected days of the week. To avoid setting this filter, do not select any option for this field.
    Day of month maskSpecify a value to run the task only on the selected days of a month. For example, 5, 9, 18, 27 – 31.
    Apply mask validationSelect False to temporarily turn off the mask validation without removing any values. The default selection is True.
    Execute after timeSpecify a value in the hours:minutes format (for example, 05:00 or 16:00) to wait before the task is run. The task run begins only after the specified time is elapsed.
    EnqueueableSpecify whether you want to ignore the next run command or run it after the current task. Select one of the following options:
    • False: Ignores the next run command when a particular task is already running. This is the default selection.
    • True: Starts the next run command immediately after the current running task is completed.

  3. Click Save.
    The ETL tasks page shows the details of the newly configured BMC TrueSight Operations Management ETL.

Step III. Run the ETL

After you configure the ETL, you can run it to collect data. You can run the ETL in the following modes:

A. Simulation mode: Only validates connection to the data source, does not collect data. Use this mode when you want to run the ETL for the first time or after you make any changes to the ETL configuration.

B. Production mode: Collects data from the data source.

Note

ProactiveNet Performance Management or TrueSight Infrastructure Management has a scheduled refresh of its data once a day. By default, the refresh starts at 3:30 A.M. Ensure that the ETL run is scheduled after this refresh completes.

A. Running the ETL in the simulation mode

To run the ETL in the simulation mode:

  1. In the TrueSight Capacity Optimization console, navigate to Administration ETL & System Tasks, and select ETL tasks.
  2. On the ETL tasks page, click the ETL. The ETL details are displayed.


  3. In the Run configurations table, click Edit  to modify the ETL configuration settings.
  4. On the Run configuration tab, ensure that the Execute in simulation mode option is set to Yes, and click Save.
  5. Click Run active configuration. A confirmation message about the ETL run job submission is displayed.
  6. On the ETL tasks page, check the ETL run status in the Last exit column.
    OK Indicates that the ETL ran without any error. You are ready to run the ETL in the production mode.
  7.  If the ETL run status is Warning, Error, or Failed:
    1. On the ETL tasks page, click  in the last column of the ETL name row.
    2. Check the log and reconfigure the ETL if required.
    3. Run the ETL again.
    4. Repeat these steps until the ETL run status changes to OK.

B. Running the ETL in the production mode

You can run the ETL manually when required or schedule it to run at a specified time.

Running the ETL manually

  1. On the ETL tasks page, click the ETL. The ETL details are displayed.
  2. In the Run configurations table, click Edit  to modify the ETL configuration settings. The Edit run configuration page is displayed.
  3. On the Run configuration tab, select No for the Execute in simulation mode option, and click Save.
  4. To run the ETL immediately, click Run active configuration. A confirmation message about the ETL run job submission is displayed.
    When the ETL is run, it collects data from the source and transfers it to the TrueSight Capacity Optimization database.

Scheduling the ETL run

By default, the ETL is scheduled to run daily. You can customize this schedule by changing the frequency and period of running the ETL.

To configure the ETL run schedule:

  1. On the ETL tasks page, click the ETL, and click Edit. The ETL details are displayed.
  2. On the Edit task page, do the following, and click Save:

    • Specify a unique name and description for the ETL task.
    • In the Maximum execution time before warning field, specify the duration for which the ETL must run before generating warnings or alerts, if any.
    • Select a predefined or custom frequency for starting the ETL run. The default selection is Predefined.
    • Select the task group and the scheduler to which you want to assign the ETL task.
  3. Click Schedule. A message confirming the scheduling job submission is displayed.
    When the ETL runs as scheduled, it collects data from the source and transfers it to the TrueSight Capacity Optimization database.

Step IV. Verify data collection

Verify that the ETL ran successfully and check whether the TrueSight Operations Management data is refreshed in the Workspace.

To verify whether the ETL ran successfully:

  1. In the TrueSight Capacity Optimization console, click Administration > ETL and System Tasks > ETL tasks.
  2. In the Last exec time column corresponding to the ETL name, verify that the current date and time are displayed.

To verify that the TrueSight Operations Management data is refreshed:

  1. In the TrueSight Capacity Optimization console, click Workspace.
  2. Expand BMC TrueSight Operations Management 9.0/9.5/9.6/10.0 Generic view extractor > Systems.
  3. In the left pane, verify that the hierarchy displays the TrueSight Operations Management instances.
  4. Click a TrueSight Operations Management instance, and click the Metrics tab in the right pane.
  5. Check if the Last Activity column in the Configuration metrics and Performance metrics tables displays the current date.

Finding view names in the BPPM database

The following tables show patterns for naming the views that are used to store PATROL data.

For BPPM version 9.5 and later:

View name pattern

Contents

_PATROL__appclassname_ST_VIEWraw stats
_PATROL__appclassname_RT_VIEW  rate stats
_PATROL__appclassname_BL_VIEW  baseline data
_PATROL__appclassname_CFG_VIEW  instance information on all config attributes

Example:

Application class name = VSM_MEMORY_V2

Hierarchy for application class = /VSM/VSM_VC/VSM_DATACENTER/VSM_CLUSTER/VSM_RESOURCE_POOL/VSM_VM

View name for stats data is: _PATROL__VSM_MEMORY_V2_ST_VIEW

For BPPM version 9.0:

View name pattern

Contents

_PATROL__full-path-appclassname_ST_VIEWraw stats
_PATROL__full-path-appclassname_RT_VIEW rate stats
_PATROL__full-path-appclassname_BL_VIEW baseline data
_PATROL__full-path-appclassname_CFG_VIEW instance information on all config attributes

Example:

Application class name = VSM_MEMORY_V2

Hierarchy for application class =  /VSM/VSM_VC/VSM_DATACENTER/VSM_CLUSTER/VSM_RESOURCE_POOL/VSM_VM

View name for stats data is: _PATROL__VSM_VSM_VC_VSM_DATACENTER_VSM_CLUSTER_VSM_RESOURCE_POOL_VSM_VM_VSM_MEMORY_V2_ST_VIEW

Was this page helpful? Yes No Submitting... Thank you

Comments