Event History shows what is stored in /usr/OV/log/ovevent.log. But this
file is only 2 Meg in size and cannot be increased beyond that. Event
history is meant to be a way to get an event window gui to look at old
events, but "old" only in the sense of the recent past. It is not good for
looking at really old events, since the ovevent file continually grows and
scrolls of the oldest ones.. Most folks who want to work with really old
events do that by saving trapd.log.
Events are written to the ovevent.log file by the ems_log_agent (ovelmd)
after they have been passed by the ems_sieve_daemon (ovesmd), so when the
daemons are down, no new ones are logged here or in trapd.log. They would
just be lost.
Could the reason you asked this question because you brought up Events
History and were expecting it to be immediately populated like a regular
events window, but all you saw was a blank screen?
You have to click on the "Query" button and then on "Display Event" before
the window will fill. This is so that you could apply a more restrictive
filter before doing that (use the Options ... Filter Control button for
that) before populating the workspace.
The default is to get everything in the file. It will not include "Log
Only" nor "Don't Log or Display" events.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Sean Goldsworthy <seang@CA.IBM.COM> on 02/16/99 01:53:22 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: James Shanks)
Subject: Question on Event History....
Hello All...
I have a question regarding the Netview Event History....
After Netview is stopped, i.e. ovstop to stop ALL the daemons, we lose all
of the current events.
By default, will the Event History show all the past events stored in a
log? Or, does some kind of filter need to be created?
Any help apprecietd.
Sean Goldsworthy.
|