Re: [nv-l] Ruleset problem with Netview 7.1.4 running RedHat Linux AS 2.
As a general rule you do NOT want to make a query smartset your first
entry in any ruleset.
Query smartset is expensive, so you want to be sure you do it only on
the events you really need
Filter by the event first, then go to a smartset and actions or whatever:
-> Action - Send email
-> Node Down > Query Smartset \(slot 1)
Reset on Match > Pager > Action send email
-> Node Up > Query Smartset /(slot 2)
Also, make sure your smartset has the nodes in the there that you are
Running "nvUtil l <smartsetname>" should show you the members of that
sure the smartset is not blue on the map.
Glen Warn wrote:
I'm trying to build a ruleset that looks something like this (see
below) I am not a seasoned ruleset builder so please keep that in
mind if you reply!
Action - Email (historical log of node Down trap)
->Node Down Trap ->
Event Stream -> -> Reset on Match
-> Pager -> Action - Email (historical log of paged event)
->Node Up Trap ->
This works just fine but has not event attribute filtering (like
source host). If I insert an Event Attribute #2 right after the Event
Stream or before the Pager - it works perfectly. Problem is, I want
to query a smartset because I have so many different hosts that need
this rule. When I do insert the Query Smartset (in either of the 2
positions described above) - the rule stops functioning. I am using
Object ID Source = 2 and using a smartset that includes the servers I
want to monitor.
PEMCO Corporation Computer Services (PCCS)
Archive operated by Skills 1st Ltd
See also: The NetView Web