×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC Helix Continuous Optimization 22.2 ... Collecting data Out-of-the-box ETLs On-premises ETLs Generic extractors and parsers to integrate data

Generic - Events SQL Extractor

This topic describes how to import generic events by using the Events SQL Extractor.

Collecting data by using the Generic - Events SQL extractor

To collect data by using the Generic - Events SQL ETL, do the following tasks:

Related topics

Dataset reference for ETL tasks

Horizontal and Vertical datasets

Developing custom ETLs

Viewing datasets and metrics by dataset and ETL module 

Step I. Configure the ETL

You must configure the ETL to connect to the file parser 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.

To configure the basic properties of the ETL

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

To configure the basic properties:

  1. Navigate to Administration > ETL & System Tasks, and select ETL tasks.

  2. On the ETL tasks page, click Add > Add ETL. 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 Generic - Events SQL Extractor from the ETL Module list. 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 the entity catalog name that is shared between ETLs.
    • Private Entity Catalog: Select if you want to use this ETL independently.

  5. Click the SQL query tab, and configure the following properties:

    PropertyDescription
    SQL query hintsProvides hints for including the mandatory and optional parameters in the SQL extraction query.
    SQL queryThis tab is only available when a custom database query has to be built in order to get the data from a generic source. Type the SQL extraction query in the text box.

  6. Click the Connection properties tab to configure the following properties:

    Property

    Description

    Datasource type

    Select 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 list.

        • Oracle
        • Microsoft SQL Server/Sybase
        • Other database

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

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

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

      • Data source name (Applicable to Microsoft SQL Server/Sybase): Specify the data source name.
      • Database name (Applicable to Microsoft SQL Server/Sybase): Type in the database name.
      • Connection URL (Applicable to Other database): Enter the connection URL. If you select Other database in the Database type property, then you must type a value.
        To connect to another database type, verify that the correct driver is installed on the Continuous Optimization server running this ETL. For an ETL in Perl code, install an appropriate DBD driver. For an ETL in Java code, install an appropriate JDBC driver.

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

    PropertyDescription
    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. The EVDAT - Event data dataset is selected by default. 

    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 any one of the following options:

    • leave all new entities in 'Newly Discovered'.
    • move all new entities in a new Domain.
      • New domain: Create a new domain. Specify the following properties under New domain:
        • Parent: Select a parent domain for your new domain from the domain selector control.
        • Name: Specify a name for your new domain.
    • move all new entities in an existing Domain 
      • Domain: Select an existing domain from the domain selector control.
    PropertyDescription
    Task groupSelect a task group to classify the ETL.
    Running on schedulerSelect a scheduler for running the ETL. For cloud ETLs, use the scheduler that is preconfigured in Helix. For on-premises ETLs, use the scheduler that runs on the Remote ETL Engine.
    Maximum execution time before warningIndicates the number of hours, minutes, or days for which the ETL must run before generating warnings or alerts.
    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.
    • Custom: Specify a custom frequency, select an appropriate unit of time, and then specify a day and a time to start the ETL run.

  8. Click Save.
    The ETL tasks page shows the details of the newly configured Generic - Events SQL extractor.

To configure the advanced properties of the ETL (optional)

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:

    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. The EVDAT - Event data dataset is selected by default. 

    Default last counterSet the default last counter in dd/mm/yyy hh:mm:ss format.

    Click the Format customization tab and configure the following property:

    PropertyDescription
    Timestamp formatSpecify a format that should be used by the ETL if the user tables or CSV files use an unsupported format. <YYYY-MM-DD HH:MM:SS> is the supported format. Depending on the type of ETL used, you might need to specify a custom format.

    Click the SQL query tab and configure the following property:

    PropertyDescription
    Lastcounter column

    Specify which is the lastcounter column that will be used to identify new data; generally this is set as the timestamp (TS).

    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.
    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

    Continuous Optimization loader output file name

    The name of the file that is generated by the Continuous Optimization loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID

    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.
    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 Continuous Optimization. It uses one of the other ETLs that share a lookup to create a new entity. The default selection is False.

    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 Generic - Events SQL extractor.

Step II. 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.

A. To run the ETL in the simulation mode

To run the ETL in the simulation mode:

  1. 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, clickin 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. To run the ETL in the production mode

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

To run 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 runs, it collects data from the source and transfers it to the BMC Helix Continuous Optimization database.

To schedule the ETL run in the production mode

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 task. 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 BMC Helix Continuous Optimization database.

Step III. Verify data collection

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

To verify whether the ETL ran successfully:

  1. 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 view the events:

  1. Access the required domain by navigating to Workspace > Domains, Services & Applications.
  2. In the details page of the domain, that appears on the right, click Navigate to > Events. 

Configuring the ETL

Below is an example query that can be used to extract generic events; it can be used as template to create custom extraction queries:

SELECT
	CONVERT(VARCHAR,EventTimeStamp,120) AS EVENTTS,
	Description AS DESCRIPTION,
	EventID AS DS_EVENTID,
	SystemName AS DS_SYSNM,
        1 AS EVENTTYPEID,
	EventName NAME
FROM
	CAPIF_Event
where EventTimeStamp > CONVERT(datetime,?, 120)
ORDER BY EventTimeStamp asc

Notes

EVENTTS column has to be set as first column. Lastcounter parameter is mandatory in the query.

Columns in the query have the same names as of the EVDAT columns. All the columns defined in the EVDAT dataset are supported. For information about the EVDAT dataset, see Dataset reference for ETL tasks.

Below is a list of supported event types:

ID

Description

1

Incident

2

Generic

3

Maintenance

4

Change

5

Problem

6

Error

7

Unknown type

Was this page helpful? Yes No Submitting... Thank you
Last modified by Shweta Patil on May 17, 2022
generic events sql etls extractors

Comments

Log in or register to comment.

Generic - Domain extractor importer
Generic - General Text Log Parser
© Copyright 2019 - 2022 BMC Software, Inc. © Copyright 2019 - 2022 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.