I have dependences
set, and it does exactly as you want. It will only send a message for the item
down, and not the items that depend on it. The system will not monitor
anything that depends on an item that is down. The system will show them as
unreachable though.
For
example:
Say you have 15
servers behind a router. You monitor all the systems and the router = 16
items.
Currently, if the
router goes down, you will get 16 messages. However, if you set the up
dependencies on all the servers to point to the router, when the router goes
down, you will only get one message stating the router is down. When you look
at the console though, it will show them as all being down. When the router
comes back up, you will only get one up message as well.
Make sure you get the
items ordered correctly on the map for the dependencies to work properly.
There is some good info in the HELP section on how to set them up
properly.
Dan
-----Original
Message-----
From:
Hoekenschnieder, Hokie (Tim G) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 12:35
PM
To:
'[EMAIL PROTECTED]'
Subject: [WhatsUp Forum] WUG and mass
notifications not wanted
Running WUG 8.x and would like to
reduce the total notifications. Let's say one device goes down and so
WUG can't see 15 other devices because of the one device being down. So
each device gets an alarm and sends out notices (1+15=16 notices). Just
one would be nice and maybe it lists all items down.
It just gets hard when at 1AM your
pager goes off, 16 times. When only one device caused it.
I started setting dependences but
worry that it will still send mass notices. We have a duty person and
after a set number of minutes the rest of the IT staff gets paged. One
network device goes down, email gets queued and then when it comes back up (16
notices x 5 people + system up notices = unhappy
campers)
