O'Reilly logo

Event Management and Best Practices by Michael Wallace, Guilherme Pereira, Jacqueline Meckwood, Peter Glasmacher, Tony Bhe

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

210 Event Management and Best Practices
Using console filters
Use console filters to filter the events in the working queue based on severity,
status, and operator ownership, to help you focus on important events. When you
filter events inside one event group, other event groups are not affected.
6.1.3 Filtering and forwarding using IBM Tivoli Monitoring
IBM Tivoli Monitoring is an agent used to monitor systems for certain conditions,
and as such, an event source. There are a few ways to configure it to filter
unwanted events from occurring.
Only deploy resource models of interest
If you are using NetView, for example, to do network performance monitoring,
you may not want duplicate information from IBM Tivoli Monitoring. Therefore,
you do not use the network interface resource model.
Forward events of interest and suppressing others
IBM Tivoli Monitoring has the means of filtering before an event is even sent to
IBM Tivoli Enterprise Console. When you configure your IBM Tivoli Monitoring
Resource Models, set them to send an event only after all of your requirements
for defining that problem are met. You can set up your resource models to only
send an event after a problem occurs based on an algorithm which you specify
using holes and occurrences, or only forwarding an event when a certain
threshold is met.
When you set this up, consider that, when you send an event, you only want to
send events for problems that require action.
You can either configure this in the default Resource Models that are supplied
with IBM Tivoli Monitoring or by modifying the profiles through the Tivoli
Framework desktop as shown in Figure 6-9.
Chapter 6. Event management products and best practices 211
Figure 6-9 IBM Tivoli Monitoring resource model profile
Optionally, you can modify the definition of the resource model via the Resource
Model Builder (RMB) utility provided with IBM Tivoli Monitoring. Using this option
only changes the default actions of the resource model. The Tivoli Administrator
can still change those attributes via the Tivoli Desktop within the IBM Tivoli
Monitoring resource model profile.
Separate profiles to limit which machines send which
messages
If you are interested in seeing a certain event type from only a subset of
machines, create a separate IBM Tivoli Monitoring profile for distribution to those
machines. Configure the appropriate resource model to send the event in the
profile distributed to those machines and to not send an event when defined in
other profiles distributed to other machines.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required