On 27 Apr 2010, at 17:43, Daniel Rich wrote:
I need to take some time to read that documentation a little more
closely....
The problem we have run into is two-fold, we have separate groups for
hardware and software. The hardware group doesn't want to receive
notifications for software problems, and in most cases, the software
group doesn't care if a host is down because the hardware group is
going
to deal with it.
So for example, the mail team needs to receive notifications for mail
being down on any server, but doesn't want to be a contact for the
server iteself. In the same vein, the hardware team doesn't need to
receive any service notifications, they just want to know if the host
goes down.
The contact groups are based on the host group/service group
intersection. This will involve lists of services. We deliberately add
the hosts into this contact group as well because if an alert is
suppressed because of a host failure, you should be told about the
host error.
What you want is to only alert, on a per contact basis, just hosts or
just services. You can do that by filtering the notification options
so that your hardware teams only get alerts about host failures and
your software teams only get alerts about services.
(My guess is that you'll have some "services" which are hardware
related that the hardware teams will want notifications about, eg, fan
checks, chassis temperatures, disk controllers, etc).
You'll have to try and see if you can get a reasonable configuration
based on the current system. Admittedly, we probably haven't
simplified it enough if you need to ask questions about it.
Ton
_______________________________________________
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users
