Ton Voon wrote: > > On 20 Apr 2010, at 22:19, Daniel Rich wrote: > >> I thought I understood how notifications work in Opsview (3.5.2 on Red >> Hat Enterprise 5), but apparently they don't work quite the way I think >> they do. >> >> We had an issue where one of our users wasn't getting notified of host >> outages for a hostgroup that he was authorized for. I looked at the >> Nagios config and there were no contactgroups listed in his contact >> record. After a couple of days of fiddling with the host and service >> groups, I found that the contact configuration will only contain hosts >> where he is *also* the contact for one or more services on those hosts. >> Also that he will only be notified about services where he is in both >> the hostgroup and servicegroup for those services. >> >> For example, if I have the following >> >> * hosta - hostgroup aa >> o mail - servicegroup mail >> o snmp - servicegroup monitoring >> o nrpe - servicegroup monitoring >> * hostb - hostgroup bb >> o mail - servicegroup mail >> o snmp - servicegroup monitoring >> o nrpe - servicegroup monitoring >> >> If I check hostgroup aa and nothing else, my user will receive no >> notifications. >> If I check hostgroup aa and servicegroup monitoring, he will receive >> notifications for hosta and the snmp and nrpe services only on hosta >> >> I really think the host groups and service groups need to be uncoupled >> in the notifications. If I am a contact for hostgroup bb, then I should >> get notified of events for for hostb, whether or not I am a member of >> any servicesgroups on that host. > > Documentation on object selection is here: > * > http://docs.opsview.org/doku.php?id=opsview-community:access#selection_of_objects > > There's a note re: host selection only if a service is in that host. > As the note says, the reason we only choose hosts only where a service > exists is because of manageability. If you select "All host groups" > but choose only the "Mail" service group, then hosts that do not have > any mail services will not be selected. We think this is right because > you do not want to give access to that other non-mail hosts unnecessarily. > > I've updated the best practices document to include a "duplicate of > host check as a service check": > * http://docs.opsview.org/doku.php?id=opsview-community:bestpractices > > >> Along the same lines, if I am a >> contact for servicegroup monitoring, I expect notifications for all >> services in that group, not just ones where I am also a contact for the >> hostgroup that host happens to be in. > > As explained above, you can achieve this by saying "all host groups" > with the selected service groups. > > Does that explain it? Does that cover your requirements? > > Ton
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. This becomes more of an issue where we have separate contacts for e-mail and text messages, as we might want to set up the host to send a text message and the services to only e-mail. As I understand the current way Opsview handles this, there is no way to do that as the text-message contact must be a contact for at least one service on the host in order to receive notifications. Personally, I think that the hostgroup and servicegroup notifications should be separate and distinct, not linked as they are in the current system. -- Dan Rich <dr...@employees.org> | http://www.employees.org/~drich/ | "Step up to red alert!" "Are you sure, sir? | It means changing the bulb in the sign..." | - Red Dwarf (BBC)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Opsview-users mailing list Opsview-users@lists.opsview.org http://lists.opsview.org/lists/listinfo/opsview-users
