Importing events


Events can be automatically imported through ETLs. The steps involved in importing events are described below:

  1. Raw events are extracted from a data source through an ETL task. When importing macro events, ETLs can use a specific dataset (EVDAT) that makes it possible to import events from a ticket or alert management platform.
  2. Lookup information has to be specified while populating the EVDAT dataset in order to properly assign the events to desired entities.
  3. For each lookup, the DS_EVENTID should be specified. For each event that is created, the DS_EVENTID must be unique. If an imported event contains the same ID, the event is discarded. 
  4. Event integration services will automatically perform lookup and classification.
  5. After the import process is complete, the events are available to the user for manual editing. They can be displayed in analysis charts and views.

To avoid duplicates, the lookup of the event for which the DS_EVENTID column is used must be unique. The lookup of a system, workload, or domain to which the event must be associated is mandatory. Providing proper lookup information allows the association of given events to proper entities populated in BMC Helix Continuous Optimization. Proper lookup columns (DS_SYSNM, DS_WKLDNM, DS_APPNM) must be specified based on the entity type (System/Business Driver/Domain).

For information and examples about how EVDAT dataset can be populated, see the Generic-Events-CSV-parser.

To import new events in BMC Helix Continuous Optimization, configure an ETL that populates the dataset EVDAT by navigating to the Administration> ETL & SYSTEM TASKS > Add > Add ETL and run the ETL. Use the following out-of-the-box ETLs to import external events in BMC Helix Continuous Optimization:

The EVDAT dataset


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*