manual

GFI Network Server Monitor Monitoring checks status  105
In both normal and mobile device view, the communication between
the web browser (i.e., Internet Explorer) and the computer running GFI
Network Server Monitor is carried out via port 11695.
By default, GFI Network Server Monitor includes a small footprint web
server which can be set up from the configuration. This avoids having
to install and configure IIS to display your network status information
on screen.
NOTE: For security reasons, we recommend the use of Microsoft IIS
web server for accessing and viewing the state of your monitoring
checks. For further information on IIS web server setup, refer to the
„Configuring IIS as the web server‟ section in the „General Options‟
chapter.
NOTE: The default port used can be customized from Configuration >
General Options > Web Server.
Check state indicators
Check state indicators are images which graphically define the current
state of your monitoring checks. The following is a list of states which
any monitoring check can have:
 Queued – Check is waiting to be processed.
 Success – Check successful.
 Failure – Check not successful/failed. A check is not marked as
failed on the first unsuccessful result. At first, the check is placed
under a 'Pending Failure' state. After some time, the check is re-
run to verify that the check is indeed failing. Once a failure
threshold (configured in the check/folder properties) is exceeded,
the check is deemed to be definitely failing and placed in the
"Failure" state. For more information on errors and error threshold
parameters, please refer to the „Configure monitor check
properties‟ chapter in this manual.
 Disabled – User configured this check not to be run. For more
information on how to enable/disable checks, please refer to the
„Enable or disable checks‟ section in this manual.
 Not Monitored – Check cannot be processed by the GFI
Network Server Monitor engine. This occurs when the monitoring
service is stopped or when a check requires a particular service
(e.g., the SNMP or WMI service) which is not available on the
target computer.
 Server in Maintenance – Check has been executed against a
target computer during its maintenance hours. When this happens
no actions are triggered (E.g., no alerts are sent).
 Failure by Dependee – The check was not executed because a
dependency check has already failed, e.g., if the router cannot be
pinged, do not check that services running on that router are
working.
 Pending failure – Check has failed but did not exceed the error
threshold level required to move a check from the 'Pending Failure'
state to the 'Failed' state.