IBM Tivoli Netcool/OMNIbus, Version 7.4

Filtering events at the source

One of the problems associated with event management is working with the high volume of events that devices can generate. You can address this problem by filtering events at the source.

A high volume of events can be generated, for example, if a router has dropped below a key performance threshold, such as the amount of time to return a ping. Typically, the router would be set to generate an event every 30 seconds until an operator has found and addressed the underlying problem. This would cause redundant events to flood the event console, impacting the problem-solving process.

Tivoli Event Integration Facility addresses this problem with two powerful techniques for analyzing, summarizing, and distributing the incoming event information:
Filtering with configuration files
By using configuration files on adapters and gateways, you can filter events based on matches to event classes.
This is the simpler and limited option in terms of capabilities.
When defined correctly, configuration files optimize event management by minimizing the number of events that each operator must monitor.


Feedback