[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

2446.0. "notify logging" by ICS::WOODCOCK () Thu Feb 27 1992 11:42

Hi there,

Notification logging: great work..

I noticed that FULL seems to log immediately but BRIEF and BRIEF + ALARM
start to log after 3 minutes then each 5 minutes thereafter. Are these on
a scheduler or a function of number of Notifies received??

Also, as a suggestion I'd try to make the BRIEF even more BRIEFER.

Example:

Alarm:  critical        Node4 NOCMAN_NS:.BBPK04 Circuit SYN-0   Rule bbpk04_0 
has fired 27-FEB-1992 11:12:45.62 Domain NOCMAN_NS:.PK

O-24    [69,1]


The above three lines show two lines when typing the file at width=132. It
would be nice if best effort was made to keep the BRIEF within 132 characters.
My choice would be to parse out "NOCMAN_NS:" in both places and also
"has fired" (we know it fired that's why it's there). This saves 29 characters
in this example. You counld even try to get rid of the decimal section on
the seconds within the time.

This would make searchs thru the file much cleaner.

kind regards,
brad...

T.R	Title	User	Personal Name	Date	Lines
2446.1	thanks	TOOK::CALLANDER	MCC = My Constant Companion	`Tue Apr 07 1992 13:31`	12
	thanks for the kudos and the great feedback. Unluckily we are too far along in the schedule to make any additional changes, but they will be considered for future enhancments. Most of the details of the logger are actually setable parameters (customizable). Most can be customized via the menu but a few can only be modified through the notification resource file (yes, the notification and NOT the mcc_resource.dat). Notification has its' own resource file so as to allow for the independent packaging of the notification (as well as a few other reasons).
2446.2	more info	DADA::DITMARS	Pete	`Tue Apr 07 1992 13:59`	24
	Like Jill said, it's late for changes, but we'll keep the suggestions for the future. We must ship V1.2. Soon. >The above three lines show two lines when typing the file at width=132. It >would be nice if best effort was made to keep the BRIEF within 132 characters. A noble idea... BRIEF and BRIEF-PLUS were aimed more at a parseable format than a readable one. Fields are separated by TAB characters and there's no fixed length for any field. >My choice would be to parse out "NOCMAN_NS:" in both places and also It will be coming off the entity name, but probably not the domain. >"has fired" (we know it fired that's why it's there). There are "has encountered an exception" and "has been disabled" messages as well, so we have to have some way of distinguishing them. >You counld even try to get rid of the decimal section on >the seconds within the time. Actually, you can do that via the MCC_TIME_ABS_TRUNC logical. Set it to the length of the longest timestamp you'll ever need.
2446.3	logging lag	DADA::DITMARS	Pete	`Tue Apr 07 1992 14:14`	7
	Hmmm... I did have a flush interval in earlier baselevels which might account for what you're seeing (RMS flushing after 1 for FULL format, which is large, vs my explicit flush after 10 brief/brief-plus format notifications). Call me so we can chat about the details.
2446.4	notification logging and purging.	CX3PT2::EMAWIZ::T_MILTON		`Tue Mar 02 1993 13:04`	7
	Hello, Is there any way to supress the fileview notification logging window that is created everytime a logging purge occurs? Ted.
2446.5	don't set commands to automatically log	GOSTE::CALLANDER		`Mon Mar 29 1993 18:54`	4
	do you have purge defined on your system to automatically log, and delete set up the same way? if so that it what is most likely causing it.