|
Hi Jay,
Here are some answers:
>> Q1 Is there any limits or restrictions in the combination of "or" and
>> "and" in the rules?
Currently ALARMS does not allow logical operators in the rule expresion.
You can use these relational operators: equal ( = ), not equal ( <> ),
greater-than ( > ), greater-than-or-equal ( >= ) less-than ( < ) and
less-than-or-equal ( <= ). These are used for comparing an attribute
to a value you choose.
You can use the CHANGE_OF syntax to watch for a change of value, but
no ANDs and ORs yet. Sorry.
We hope to provide support for the logical operators soon, but not yet.
>> Q2 Can a rule when tripped run a .com file?
Yes, that's exactly what it is designed to do. When you create your
rule, you can specify a DCL command procedure to run when the rule
fires and one to run when the rule encounters an error.
MCC> CREATE MCC 0 ALARMS RULE my_rule -
EXPRESSION = (NODE4 FOO user bytes sent > 3452), -
PROCEDURE = <enter your procedure here> , -
EXCEPTION HANDLER = <enter your procedure here> , -
PARAMETER = <a string to pass to your command procedure in P7>
There are six example command procedures provided with ALARMS. These
log notifications and errors to a file, mail notifications and errors
to whomever you chose, and broadcast notifications and errors to your
terminal.
The command procedures you write have available to them, these pieces
of information: The rule name that fired or had a problem
The rule description
The rule category
The rule expression
The time the rule fired or had an error
The evidence that caused your procedure to run
Any information you provide in the PARAMETER argument
The severity
and the Domain in which the rule was running.
See example command procedures to see how they can be used.
>> Q3 When doing the demo two severities, "warning" and "critical", are shown.
>> Are there any other severities?
There are five: CRITICAL, MAJOR, MINOR, WARNING, and CLEAR
>> Q4 Is it possible to write a rule once and have it apply to a number of
>> nodes, i.e. all node4 entities?
In V1.1 you can do sub-entity wildcarding, but in V1.2 we will support
full wildcarding for global entities. The global wildcarding will work
within the domain that the rule is in. So in terms of your example, yes
the rule will apply to all node4 entities within a domain.
>> Q5 The list of third parties includes Apple and Microsoft. Can anyone
provide detail and their involvement and what capabilities will be
forthcoming?
I'll leave this one open for someone else to answer.
aud...
|