You should now be
comfortable with the creation, removal and modification of Host Groups, the
moving of Hosts within these Host Group, the creation of Hosts and their configuration.
After the Host Groups
and Hosts have been configured, Users can begin to interpret their current status and analyze
the monitored data within the ‘Host Groups, Hosts and Services’ section of
This section is the
default view for all Host Group, Host and Service Check analysis and allows a
range of functions including investigation of Hosts and services, ‘actions’ at
a Host Group/Host Service Check level (actions are covered later) and more.
The ‘Host Group, Hosts
and Services’ section is split into two ‘sections’; the top half is known as the
‘Navigator’ and the bottom half is
known as the ‘Checker’.
Example ‘Host Group, Hosts and
Services’ section with one Host selected
The navigator contains the Host Group
hierarchy, with the Hosts as the ‘end point’. In the example screen below,
there is a Host Group hierarchy containing four Hosts:
Example ‘Navigator’ with 4 Host
Groups expanded to reveal 4 Hosts
To view the details
of a Host, you/user should check the ‘View’ box next to the Host’s contextual
menu. Checking the box will display the checker window and populate it with the Service Checks of the Host(s) selected.
The checker only contains the Service Checks
from the Hosts who have been selected within the navigator. For example, if you
select the Host ‘opsview’ then the checker will appear and display all of the
service checks for the ‘opsview’ Host. Note: The checker will not be covered in this
section, instead the documentation covering ‘Service Groups, Service Checks and
Host Templates’ will cover it in detail.
The navigator has a column on the left
where the Host Groups and Hosts can be viewed and interacted with, via the
contextual menu. There is also the ‘View’ column, where you can select Hosts to
display within the checker.
The right-half of the
navigator contains the status information for both the Hosts and their Service Checks. The status information is split into two sections; ‘Host Status’ and
‘Service Status’ columns. Host Status refers
to the state of the Host as defined by the results of the Host Check Command
associated with it. The Service Status refers
to the service checks running on those Hosts. In the screen below we have examples
of where the Hosts are ‘DOWN’ (denoted as ‘dn’), meaning the Host Check Command
has failed to get a response from the Host. There are also examples of failed
service checks (CRITICAL (cr), UNKNOWN (un) and WARNING (wn)).
Host’s that have an
‘OK’ status from the Host Check Command are categorised as ‘UP’. In the example
below there are 20 Hosts that are ‘UP’ and 3 Hosts that are ‘DOWN’.
Example Host Group Navigator
with failed Hosts
Each of the ‘Host’/’Service
Status’ columns are split into ‘Handled’ and ‘Unhandled’ respectively.
‘Handled’ /‘Unhandled’ refers to whether the non-OK status of a Host or Service Check has been acknowledged by a User. For example, when a Host fails (i.e.
changes into a non-OK state), it will initially go into the ‘Unhandled’ column. The same logic applies for service checks.
In order to convert
an Unhandled problem into a Handled problem, you must ‘ACKNOWLEDGE’ it. This can be done via the contextual menu, either at a Host Group, Host
or Service Check level. In the example below, we are going to ACKNOWLEDGE all
unhandled problems with the ‘Monitoring Servers’ Host Group by clicking ‘Mass
Acknowledgement’ within the contextual menu:
Contextual menu against
‘Monitoring Servers’ Host Group
Once the contextual
menu is clicked, a modal window will appear confirming the items that are to be
acknowledged. This window is covered later in the document, along with all the
other contextual menu items and their respective modal windows.
For reference, an ‘UP’ Host,
or an ‘OK’ Service Check command are automatically considered handled by the
Opsview Monitor software.