Events can be automatically imported through ETLs. The steps involved in importing events are described below:
- 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.
- Lookup information has to be specified while populating the EVDAT dataset in order to properly assign the events to desired entities.
- 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.
- Event integration services will automatically perform lookup and classification.
- 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:
- Generic - Events CSV parser
- Generic - Events SQL Extractor
- VMware vCenter ETLs
- Oracle - Enterprise Manager extractor
The EVDAT dataset
|INTERVENTTS||Event intervent timestamp||Intervent timestamp of the event [YYYY-MM-DD HH:MI:SS]|
|PENDINGTS||Event pending timestamp||Pending timestamp of the event [YYYY-MM-DD HH:MI:SS]|
|RESOLUTIONTS||Event resolution timestamp||Resolution timestamp of the event [YYYY-MM-DD HH:MI:SS]|
|EVENTTS||Event start timestamp||Start timestamp of the event [YYYY-MM-DD HH:MI:SS]|
|DS_WKLDNM||Name of the workload in the datasource||The name of the workload to which the event is associated, as in the datasource.|
|DS_APPNM||Domain name in the Datasource||The name of the domain to which the event is associated, as in the datasource|
|ENTNM||Entity name||The name of the entity|
|ENTTYPENM||Entity type||The type of the entity|
|DS_SYSNM||Name of the system in the datasource||The name of the system to which the event is associated, as in the datasource.|
|SEVERITY||Severity||The severity of an event can be defined by using a discrete scale, ranging from 1 (lowest severity) to 5 (highest severity).|
|SRCCLASS||Event class as classified in the Datasource||A classification label used in the Datasource to classify the event; can be more detailed compared to the Event type|
|SRVUNAV||Service unavailability||Report if the event has caused service unavailability. Boolean value [true|false]|
|STTRSTA||State transition status||State transition status|
|STTRTS||State transition timestamp||State transition time of the event [YYYY-MM-DD HH:MI:SS]|
Type of the event:
|DS_EVENTID||Event identifier in the datasource||Unique event identifier in the datasource|
|CNTOCC||Count of occurrences||Count of occurrences|
|STRONGLOOKUPFIELDS||Strong lookup fields||Strong lookup fields used to perform lookup|
|WEAKLOOKUPFIELDS||Strong lookup fields||Strong lookup fields used to perform lookup|