[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

6075.0. "Getevent service and severity..." by AEOENG::BOMMART (WaveWalker 887-4108) Tue Aug 09 1994 14:46

Hello from France,

	A customer is doing strange thing (as usual...:-) and I'm wondering
	if it exists a cleaner way to do the same thing...

	This customer is writing 5 AMs, each of them offers a
	GETEVENT directive which returns an event to any client (FM, PM)
	The Events it generates are not OSI events (the argument MODE
	of the GETEVENT response is not returned)

	BUT for each of this event the customer creates a Notify request
	JUST to assign a severity to this event => color change in its map 	
	windows.

	You have guessed what happens: each time it starts its Iconic Map it
	starts a very big notification file with issues a lot of:		
       NOTIFY domain ddd entity list = (foo *), events = (eee) ! severity = sss"
	one notify request per event supported by its 5 AMs !!!!

	For me it is horrible => this method is very "thread consuming"

	Would it be possible to change its GETEVENT service in order to assign
	a target severity argument of its GETEVENTSUCCESS response.

	Its GETEVENT service would become:
		- issue a mcc_event_get
		- depending of the event code returned by the mcc event manager,
		  build a different GETEVENTSUCCESS response whith a different
		  targetseverity argument

	Is it a good method ? any problem with this approach ?

I thank you in advance,
Regards,
Damien.

T.R Title User Personal
Name Date Lines

6075.1 Yes, use target severity in getevent directive TAEC::FLAUW Marc Flauw, CEM Technical Office, VBO Wed Aug 10 1994 11:48 18

T.R	Title	User	Personal Name	Date	Lines
6075.1	Yes, use target severity in getevent directive	TAEC::FLAUW	Marc Flauw, CEM Technical Office, VBO	`Wed Aug 10 1994 11:48`	18
	Hi Damien, Always doing strange things as usual -). Modifying the getevent entry point of the AM to add a target severity as you are proposing in your note is likely to be the simplest way of solving this problem. It assumes that you have access to the sources of the AM and can modify it to generate a new AM with the modified getevent directive. Another alternative might be to use targetting to assign the severity, but it is a lot less efficient as the target rules are on a per domain basis and it is likely to have an impact onthe notification throughput. The only advantage is that it does not require to change the AM. Best regards, Marc.

Hi Damien,

Always doing strange things as usual -).

Modifying the getevent entry point of the AM to add a target severity as you are
proposing in your note is likely to be the simplest way of solving this problem.

It assumes that you have access to the sources of the AM and can modify it to
generate a new AM with the modified getevent directive.

Another alternative might be to use targetting to assign the severity, but it is
a lot less efficient as the target rules are on a per domain basis and it is
likely to have an impact onthe notification throughput. The only advantage is
that it does not require to change the AM. 

Best regards,

Marc.