Conference azur::mcc

3801.0. "Collector event type" by CTHQ::WOODCOCK () Thu Sep 24 1992 17:08

Hello,

I have begun to 'think' about using data collectors for multiple purposes
with multiple management domains in mind...on the same system. This was kinda
discussed in note 2823 but I'd like to add this to the wish list. I need
event TYPES by which I can write wildcarded alarms against. I know the API is
open but this approach isn't for non-program types and I haven't the time to
persue it even if I were. I graciously request an extra field in the SEND_EVENT
command which can be specifically alarmed against as a 'type'. An example is 
that I currently have built a large monitor using dozens of collectors. I then
wrote an alarm rule which helps process the incoming events with an expression:
exp=(occurs(collector * any event) or something like it. Now if I begin to use 
other data collectors for other purposes (different networks) the previously 
defined rule picks up the unwanted events (not good). This means I must either 
write a seperate rule for each collector (thanks, no...) or put a hook in the 
procedure to exit if it is the wrong networks event (queue costly). With a 
new field the expression would look something like:
exp=(occurs(collector * WATN_NETWORK)) etc.

Without this function the data collector becomes a ONE SOLUTION ONLY widget
which I don't think was the plan.

kind regards,
brad...

I think what you're requesting (at least on the alarms side)
has been asked for before:  to be able to alarm against the 
argument of an event.  I don't know where it stands presently 
in the priority list.  This would be useful in other situations
as well.

The syntax could be something like:

exp=(occurs(collector * any config event, 
	    with Event Type = "WATN_NETWORK"))

> The syntax could be something like:

> exp=(occurs(collector * any config event, 
>	    with Event Type = "WATN_NETWORK"))

That'll do it.

thanks for the ears,
brad...

For anyone still interested in this subject I have new info for a workaround.
It does not appear this 'event type' support will make it into V1.3 but...

Although I didn't think partial wildcarding was supported at the global level
in v1.2 the following expression works:

express=(occurs(collector .watn.* any event))

Therefore a new directory for each set of functional data collectors allows
for a viable solution for seperating alarms for collectors so they don't walk
on each other.

brad...