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

Chapter 6. Event management products and best practices 251
The other option now available with IBM Tivoli Enterprise Console 3.9 is the
Web-based console. This console runs on a WebSphere Application Server that
can be installed via the installation wizard for IBM Tivoli Enterprise Console 3.9.
You can then log in to that WebSphere Application Server via a Web page that
directs you to the IBM Tivoli Management Region where IBM Tivoli Enterprise
Console is located.
This console is only used for viewing events. No configuration can be done from
the Web console. However, operators can acknowledge, close, and run
automated tasks from the events. The Web console has its advantages in that no
software needs to be installed on a workstation before you view it. Figure 6-21
shows an example of the new IBM Tivoli Enterprise Console Web-based
console.
Figure 6-21 Example of Web console event viewer
6.4.3 Rules
You can also use rules for notification within IBM Tivoli Enterprise Console. The
most popular are described here.
252 Event Management and Best Practices
E-mailing and paging
E-mailing and paging can be handled directly from the IBM Tivoli Enterprise
Console event servers rule base. There is an out-of-the box rule set supplied for
these actions called notify.rls. This rule notifies, as defined in the rule, on the
severity of the event and the event class. You must define within this rule the
method in which you want to notify (page or e-mail) the person or group and their
addresses.
Customizing notify.rls for which events to send notifications
In the notify.rls rule, find the section shown in Example 6-18 located within the
notify_configure rule.
Example 6-18 notify_configure within the notify.rls rule set
rerecord(notify_list, 'EVENT',
['MAIL', % type of notification
- MAIL/PAGE
'Administrator', % user to notify
'Administrator@EventServer']), % user email/page
address
% Set class-specific notification information
rerecord(notify_list, 'TEC_Error',
['MAIL', % type of notification
- MAIL/PAGE
'Administrator', % user to notify
'Administrator@EventServer']) % user email/page
address
),
This section is where you set the type of notification to send the user to send it to
and their address. The top section starting with
rerecord(notify_list, 'EVENT',
sets the notification method for all events which are separated later based on
severity in the following rules. For example, if we want to send all events by
e-mail to administrator Bob at bob@company.com, we can modify this section as
shown in Example 6-19.
Note: You must activate and modify the out-of-the box rules supplied with IBM
Tivoli Enterprise Console 3.9 according to your environment so they can work
properly.
Chapter 6. Event management products and best practices 253
Example 6-19 Sending an e-mail within the notify.rls rule set
rerecord(notify_list, 'EVENT',
['MAIL', % type of notification
- MAIL/PAGE
'Bob', % user to notify
'bob@company.com']), % user email/page address
The bottom section is where you can configure notifications based on the IBM
Tivoli Enterprise Console class. In Example 6-18, the rule is configured for the
TEC_Error class to send the administrator an e-mail. If you want to send
notifications on different classes, you add them here. For example, if we want to
send an e-mail to Bob when an event comes in with the class TEC_Start, we add
an entry to this rule as shown in Example 6-20.
Example 6-20 Sending TEC_Start events via e-mail via the notify.rls rule set
rerecord(notify_list, 'TEC_Error',
['MAIL', % type of notification
- MAIL/PAGE
'Administrator', % user to notify
'Administrator@EventServer']) % user email/page
address
),
rerecord(notify_list, 'TEC_Start',
['MAIL', % type of notification
- MAIL/PAGE
'Bob', % user to notify
'bob@company.com']) % user email/page address
),
The rest of the rule deals with sending the notifications based on each type of
severity. The rules send a notification on any event if the event severity is
changed to
Fatal or Escalated. The rules also send a notification if an event is
re-opened. Table 6-6 lists the types of notification sent on each severity if the
default parameters of the rule remain unchanged.
Table 6-6 Notification types and their severities
Severity Notification Escalation
Fatal Notify via e-mail Notify via e-mail
Critical Notify via e-mail Notify via e-mail
Minor Notify via e-mail Notify via e-mail

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