[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

3162.0. "not_occurs rule" by ULYSSE::MORALES (Reddite quae sunt Caesaris Caesari) Wed Jun 10 1992 13:15

    
    With MCC we can define rules that fire when something good or bad
    happens.
    Are there any plans to allow the user to define rules that fire
    when an event does not happen within a duration (timeout) ?
    
    something like: NOT_OCCURS( ENTITY X EVENT event_name , duration)
    
    This can be useful for "watch-dogs" on applications , periodic
    testing of event sinks, etc...
    
    	
    Manuel.
T.RTitleUserPersonal
Name
DateLines
3162.1User visible syntax is very importantNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamWed Jun 10 1992 14:5131
RE: .0

>    Are there any plans to allow the user to define rules that fire
>    when an event does not happen within a duration (timeout) ?
>    something like: NOT_OCCURS( ENTITY X EVENT event_name , duration)

  Manuel,

  I have been thinking more about this since our phone conversation.
  I was thinking of using the existing OCCURS function:

	occurs( <event>, <count>, <duration> )

  but specify  0  as the count.  If the Event occurs zero times in a
  certain lengh of time ... let me know.

  Of course, for such an expression there is still a scope of interest
  time (forever is the default) which defines how long you want this
  situation monitored.

  Now .. as far as the coding efforts .. This will be interesting.  I imagine
  that a 'Thread Terminator' would be used to time-out the request for the
  event after the <duration> had expired.  If the counter was zero, then a
  rule-fired event would be generated and the process would continue.  If
  the counter was non-zero no event would be generated and the (internal)
  counter reset for the next evaluation.

  I think this is a *very* good suggestion - and should be added to the list
  of Alarms features for after v1.2

  /keith
3162.2lost events ?ULYSSE::MORALESReddite quae sunt Caesaris CaesariThu Jun 11 1992 11:4619
	Keith,

according to the use I see for this feature, such an OCCURS rule that will 
fire if 0 (ZERO) event is seen for a given duration will satisfy my
requirements (but others ??)
If MCC is supposed to receive an event every 10 minutes, after a duration 
of 10 minutes a count of zero event will generate the rule-fired event.
If I want to allow for lost events without firing the rule, a n*10 minutes
duration will allow for n-1 lost events.
But what if I want to allow to loose only 1 event among n ? 

By creating a NOT_OCCURS rule we could get more flexibility.
 
	not_occurs(entity x event,count,duration)



		Manuel.
3162.3I see nowNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamThu Jun 11 1992 12:217
  Manuel,

  I get it now 8)

  Yes .. a new function would be better for this functionality.

  /keith