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

Column nameLabel Description 
INTERVENTTSEvent intervent timestampIntervent timestamp of the event [YYYY-MM-DD HH:MI:SS]
PENDINGTSEvent pending timestampPending timestamp of the event [YYYY-MM-DD HH:MI:SS]
RESOLUTIONTSEvent resolution timestampResolution timestamp of the event [YYYY-MM-DD HH:MI:SS]
EVENTTSEvent start timestampStart timestamp of the event [YYYY-MM-DD HH:MI:SS]
DS_WKLDNMName of the workload in the datasourceThe name of the workload to which the event is associated, as in the datasource.
DS_APPNMDomain name in the DatasourceThe name of the domain to which the event is associated, as in the datasource
ENTNMEntity nameThe name of the entity
ENTTYPENMEntity typeThe type of the entity
DS_SYSNMName of the system in the datasourceThe name of the system to which the event is associated, as in the datasource.
SEVERITYSeverityThe severity of an event can be defined by using a discrete scale, ranging from 1 (lowest severity) to 5 (highest severity).
SRCCLASSEvent class as classified in the DatasourceA classification label used in the Datasource to classify the event; can be more detailed compared to the Event type
SRVUNAVService unavailabilityReport if the event has caused service unavailability. Boolean value [true|false]
STTRSTAState transition statusState transition status
STTRTSState transition timestampState transition time of the event [YYYY-MM-DD HH:MI:SS]

Type of the event:

  • 1=Not planned incident
  • 2=Planned generic
  • 3=Planned maintenance
  • 4=Planned change
  • 5=Not planned problem
  • 6=Not planned error
  • 7=Unknown
DS_EVENTIDEvent identifier in the datasourceUnique event identifier in the datasource
CNTOCCCount of occurrencesCount of occurrences
STRONGLOOKUPFIELDSStrong lookup fieldsStrong lookup fields used to perform lookup
WEAKLOOKUPFIELDSStrong lookup fieldsStrong lookup fields used to perform lookup

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