Conference csc32::consolemanager

	Simon ,
	
	It's me again...
	For some PCM events (like 'user' connects to
the console)you feed more data into the information field 
like the user-name.

	Would it be possible in the future to have a kind
of flag to tell Pcm to store event context info into this
field ? Or would this really impact overall performance.

	Thank's for your help

	Pierre

Pierre,
       nice to hear from you again.

As far as the question is concerned we can look at this. The way the CM events
are generated is different to the events received from the managed systems in
that there is no real context so we don't have to worry about log files etc.

Secondly we signal an event as soon as the match occurs i.e. we do not wait
until the whole line of text has come in to the CM system before the console
controller hands the event to ENS. The daemon will flush it's data buffer to
disk when the event occurs, but if the match occurs on the first part of a text
line it is most likely that the rest of the text will NOT be in the log file by
the time that the action routine ( Eventlist ) comes to extract it.

e.g. Imagine the following line of text is an alarm message from a managed      
     system:

Security Alarm: Break In attempt on terminal tty03 by User Simon

An event match might look like:

"Security Alarm: Break In attempt"


In this case it is likely that the text line you would see is:

"Security Alarm: Break In attempt"

This does not give the full data required for the message, whereas a user coming
along a short time later would ask for context and by this time the rest of the
data would be available.

Having said that there are ways to make it a bit better. For example in the
above case if a regular expression is used we could bound the match to an end
of line:

"Break In attempt*^"

Here the * and ^ would set the match only to occur if one of CR,FF or LF
occurs atr the end of the string.

The reasoning above coupled with the overhaed on I/O is really the reason
why we do not do this.

However, if you still wish to make an official request for this send a mail to
took::dinneen (or product manager as a Phase 0 request and we will look at it as
we would any other business proposition.

Cheers SImon..... 

	Simon ,

	Thank's for your detailed answer.
	Maybe my questions were not so clear. I understand the way 
Pcm does pattern matching. In fact i have already played with 
regular expression in the event match for OSCint/Census integration
 action routines. The event text parameter passed to the action
makes it work fine (i'll use it for Mcc/Temip and Netview re-sending)
But i haven't found this field in the startup settings of the ENS 
window. 

	My concern is to be able to offer to system managers in charge
of monitoring many systems the useful features of PCM  (like ACk..)
while still providing with the same monitoring window without 
decreasing performance capabilities of your product..ouf !
 

	I'll send a mail for Phase 0 requests , maybe the request
would be to have the event text (not context) in the startup settings 
of ENS. Then the system manager would decide which events need to 
be detailed and change the corresponding event match to the correct
regular expression. 

	Thank's again for your help

	Pierre


	

    
    
    Today I was very supprised after V1.5 installation when we noticed
    there was TEXT choice in the startup settings of multiline ENS window.
    Did you add this after V1.1? Text is also coming on the window just
    fine especially if xxxx*^ regular expression is used.
    
    

  Yup, I snook this in for the V1.5 release, we got A LOt of requests for
  this.

  WARNING: Displaying text for an event may cause a significant performance
           degradation as each event has to be "looked up" in the systems log 
           files in order to obtain the event text, this isnt too bad on
           OSF/1 or ULTRIX but is real bad news on OpenVMS. 

Cheers,
Phil