$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Log File Agent User's Guide IBM Tivoli Monitoring, Version 6.3

Event mapping

The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to Tivoli Netcool/OMNIbus or Tivoli Enterprise Console.

EIF events specify an event class, and the event data is specified as name-value pairs that identify the name of an event slot and the value for the slot. An event class can have subclasses. IBM Tivoli Monitoring provides the base event class definitions and a set of base slots that are included in all monitoring events. Agents extend the base event classes to define subclasses that include agent-specific slots. For Log File agent events, the event classes correspond to the agent attribute groups, and the agent-specific slots correspond to the attributes in the attribute group.

The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIF slots instead of using the default mapping described in this topic. For more information about EIF slot customization, see the Tivoli Enterprise Portal User's Guide.

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorder of Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agent and is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems) when application support for the agent is installed. The BAROC file for the agent and the base BAROC files provided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see "Setting up event forwarding to Tivoli Enterprise Console" in the IBM Tivoli Monitoring Installation and Setup Guide.

Each of the event classes is a child of KLO_Base and is defined in the klo.baroc (version 06.30.00) file. The KLO_Base event class can be used for generic rules processing for any event from the Tivoli Log File Agent.

For events that are generated by situations in the LFAProfiles attribute group, events are sent using the ITM_KLO_LFAPROFILES event class. This event class contains the following slots:

For events that are generated by situations in the Log File RegEx Statistics attribute group, events are sent using the ITM_KLO_LOG_FILE_REGEX_STATISTICS event class. This event class contains the following slots:

For events that are generated by situations in the Log File Status attribute group, events are sent using the ITM_KLO_LOG_FILE_STATUS event class. This event class contains the following slots:

For events that are generated by situations in the LogfileEvents attribute group, events are sent using the ITM_KLO_LOGFILEEVENTS event class. This event class contains the following slots:

For events that are generated by situations in the LogfileProfileEvents attribute group, events are sent using the ITM_KLO_LOGFILEPROFILEEVENTS event class. This event class contains the following slots:

For events that are generated by situations in the Performance Object Status attribute group, events are sent using the ITM_KLO_PERFORMANCE_OBJECT_STATUS event class. This event class contains the following slots:

For events that are generated by situations in the pro Performance Object Status attribute group, events are sent using the ITM_KLO_PRO_PERFORMANCE_OBJECT_STATUS event class. This event class contains the following slots:

For events that are generated by situations in the Thread Pool Status attribute group, events are sent using the ITM_KLO_THREAD_POOL_STATUS event class. This event class contains the following slots:


+

Search Tips   |   Advanced Search