I’m trying to figure out how I can see the relationship between contact groups-notification rules-services/hosts and contacts.
I will explain:
If a user asks me to which hosts and services do they get notifications about, I have no way of knowing that.
On Icinga director > users/contacts, I can see the contact groups assigned to this user, but I can’t see where the groups are assigned to (host, services, service sets, etc.)
Is there a module, a search, or a command that can return these sorts of connections as there is no way of simply see this from the GUI.
I know that the versions running on my instance are a bit old, but from fiddling around with newer versions I could see the same problem.
BTW, I have one master with no nodes (satellites) and no fancy stuff - just a simple, all in one and one in all () server.
Thank you for your answer, although I think I wasn’t clear enough, or didn’t understand your answer.
All hosts and services have checks that send notifications based on the threshold levels of these checks.
Now, if for example Jane Doe approaches me and asks for all the hosts and services that she might get notification from, I have no way of knowing that.
I can see her contact (not user) and to which contact-groups it is assigned, but there is no one place I can see which hosts and which services these groups are assigned to (apart from going over ~650 hosts and ~2000 services manually)
My Icinga is not synced to any AD nor do I manage users from other sources.
All contacts and contacts groups were created under Icinga Director.
Quick Edit: All contacts are defined as contacts only and not users that can login to Icinga.
They only get notifications for the relevant host or services for them with all the info contained in the message.
If they still require access to Icinga, they can use a view-only user.
Sorry for the delay as I was engaged with other projects.
Yes, the contact group is visible in the Notification part of the host (and service).
For some reason nothing comes up when searching contact groups.