Monitor, each Service Check must be assigned to a Service group; a logical container of one or more Service Checks
that is used for Notifications, access control and more. Each Service Check
must be a member of a Service Group, and can only belong to a single Service
Within a default
Opsview Monitor system, there are numerous Service Groups containing one or
more Service Checks. For example, the ‘Application – Apache HTTP Server’
contains eight Service Checks:
Service Groups like
‘Application – Apache HTTP Server’ are used in Opsview Monitor for Notifications
and also access control.
Service Groups are
used in combination with ‘host groups’ in the ‘Hosts/Services’ tab to determine
what Service Checks status changes the Users are notified for.
For example, if there
are 20 hosts within the ‘Cloud’ host group, and only 1 host has a Service Check
applied to it that is a member of the ‘Application – Apache HTTP Server ‘, then
this 1 host’s 1 Service Check is the only item that will be notified upon.
Similarly, if you wanted
to be notified only for errors on ‘Application – Apache HTTP Server’ service
checks, regardless of the host, you would select ‘-‘ in the ‘in the following
host groups:’ dropdown box, and select ‘Application – Apache HTTP Server’ in
the Service Groups box. This means that if any Apache Service Check went into a
non ‘OK’ state, then you would be notified.
Service groups can
also be used for access control; limiting Users who are members of a role by
determining what Service Groups & host groups combination they can see. For
example, you may want to only allow Users of a certain role to be able to view only
Apache Service Checks on only Apache hosts when they log-in.
To do this, you can
choose the host group containing the Apache hosts within the ‘Authorised for
Host Groups’ section, and select ‘Application – Apache HTTP’ within the
‘Authorised for Service Groups’ section.
This tells Opsview
Monitor, only show Users who are members of this role Apache Service Checks on
Apache servers when they log in.