Event Processing Interface

Administration > Event Processing > Event Processing Customizations

Scripts can be executed directly before the event enters the event pipeline, so before the resolution of CIs and ETIs takes place.

For example, you may want to execute a script at this point that sets further hints that affect the resolution of CIs and ETIs. An entry point further along the event pipeline would be too late to influence the resolution of CIs and ETIs.

Scripts can be executed directly after CI/ETI resolution, but before further processing, such as duplicate events suppression and closing related events automatically.

For example, you may want to execute a script at this entry point in the event pipeline if you want to influence how duplicate events are handled. It could be that you have duplicate events suppression enabled in general, but you are interested in changing the duplicate events suppression setting for a particular type of event, while leaving it unchanged for all other event types. So you could execute a script at this entry point that disables duplicate events suppression for the specified event type. Any entry point further along the event pipeline would be too late to influence duplicate events suppression behavior.

Scripts can be executed after all event processing has taken place, but before the event is stored in the database.

For example, at this entry point to the event pipeline, you could execute a script that makes changes to some text, or inserts a link to a knowledge base, and so on, before the event gets stored in the database.

Scripts can be executed after the event is stored in the database. In this case, the scripts are all read-only scripts, since as soon as an event is stored in the database, it can no longer be modified.

For example, you may want to execute a script at this entry point in the event pipeline to forward events of a particular type, that are already stored in the database, to another application. Or you could execute a script that writes specified events stored in the database to an audit log.

This task shows you how to create an event processing customization.

1. Open the Event Processing Customizations manager:

   Administration > Event Processing > Automation > Event Processing Customizations

   Alternatively, click Event Processing Customizations.

2. Click New or to open the Create Event Processing Customization screen.

   The button is displayed only when you open the Event Processing Customizations screen (Administration > Operations Console > Event Processing Customizations). If you are already on the Event Processing Customizations screen, click New to open the Create Event Processing Customizations screen.

3. In the General section, enter a display name, and a description (optional) of the event processing customization.

4. Select the Processing Step from the drop-down list. The options are:

   • Before CI/ETI Resolution — Selects scripts that are executed directly before the event enters the event pipeline (before the resolution of CIs and ETIs takes place).

   • After CI/ETI Resolution — Selects scripts that are executed directly after CI/ETI resolution, but before further processing, such as duplicate events suppression and closing related events automatically.

   • Before Storing Events — Selects scripts that are executed after all event processing has taken place, but before the event is stored in the database.

   • After Storing Events — Selects scripts that are executed after the event is stored in the database. In this case, the scripts are all read-only scripts, since as soon as an event is stored on the database, it can no longer be modified by further EPI scripts.

5. Select Read-Only for event processing customizations that must not modify events.

6. Under Condition, select an event filter for the mapping rule from the Event Filter list. The filter determines which events to consider in the mapping operation.

   If no appropriate filter is already configured, click the Browse (...) button, which opens the list of event filters. You can create a new filter or edit an existing one. For information about filters, see How to Define Event Filters.

7. Optional. Under Properties, click to add and order any JAR files required by the script.

   The ordering of the JAR files is used by the classpath during execution. For example:

   JAR file A contains a class x.y.z.

   JAR file B contains a class x.y.z.

   The ordering of the JAR files A and B dictates which class of which JAR file is loaded.

   Note The maximum JAR file size that you can upload is determined by Max file upload size in KB infrastructure setting (Infrastructure Settings > Foundations > Security > Security - File upload). For more information about this setting, see the online help.

8. Specify a timeout value for the script. If the script execution has not completed within the specified time, the script is ignored and an annotation is added to all affected events.

   Note If the EPI Server Timeout setting is shorter than the timeout specified for a script, the execution of the script is stopped after the global timeout period is reached. HPE recommends to select a shorter dedicated timeout value for individual scripts and set a longer global timeout.

9. Enter the event processing customization script text in the Script field.

   For information about creating scripts, see the Develop section.

   Note Maximum supported script length is 250,000 characters.

10. Select Activate after save if you want to activate the script immediately (this option is selected by default). You can also activate the script later by clicking Activate.

    Tip You can click to activate a script and to deactivate a script. Alternatively, use the opr-script command-line interface to enable or disable a script. For more information, see opr-script Command-Line Interface.

11. Select Save.