Defining event classes

An important task when you create an adapter is to determine the event classes for the information that you want to monitor. To help you when you write rules to handle the events, you must make event definitions as specific as possible.

The Probe for Tivoli EIF has a set of default rules that map attributes of Event Integration Facility events to columns in alerts.status. You must define these common attributes so that the probe can process them.

Note: Event class names must be unique.

The event string is adapter-dependent. You can have as many as required pairs of attributes and values. The following code fragment illustrates the assembly of an event string:

"MY_EVENT_CLASS;
source=_ANY_DEFINED_SOURCE;
application=myAppl1;
origin=9.179.1.234;
msg=Hello World;
END\n\001"

In the code fragment, source and application are application-specific.

For more information about probe rules and attributes, see the IBM Tivoli Netcool/OMNIbus Probe for Tivoli EIF guide in the IBM Tivoli Netcool/OMNIbus integrationsInformation Center at
http://www.ibm.com/support/knowledgecenter/en/SSSHTQ/omnibus/common/kc_welcome-444.html

For more information about the default classes hierarchy, see the IBM® Tivoli Enterprise Console Adapters Guide in the IBM Tivoli Information Center at
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp