Search:     Advanced search

Host Check

Article ID: 442
Last updated: 27 Dec, 2019
Revision: 1
Views: 0

To reduce unnecessary multiple alerts of services that may be unavailable or down when a physical server goes down, it is recommended that the Host Check be configured as the first point of configuration for most Monitor Servers. The Host Check point checks the host server where the applications/services reside to make sure it is responding. If the Host Check fails or returns an error, the points that are dependent on the Host Check will not run.


For example: If the ArcGIS® Host Check is nonresponsive, the AGS MapService and GeoCode Service check points will not run because they are dependent on the Host Check. A Host Check monitor point is a logical step in proactively monitoring systems, alleviating the need for multiple alerts if the host is unavailable.

Note: Each new point is assigned a unique ID by the SQLite database and cannot be changed. Be sure to check the ID number of the Host Check ID when assigning dependencies to the Host Check. Points can only depend on other points within the same GeoMonitor Server configuration.

 The parameters that are unique to the ArcGIS Server Streaming Service include:

Server Name

DNS name of server to be checked

Port#

Any port on the server to connect to. This is not a ‘Ping’ check, but an open port check.

Suggested ports to check:

22 = ssh; 23 = Telnet; 80 = webserver; 443 = secure webserver; 445 = MS directory services; 1433 = MS SQL; 1494 = Citrix; 1521 = Oracle listener; 1526 = alternate Oracle listener 3389 = RDP; 8080 = Apache Tomcat

Bolded ports are the most commonly used ports

Prev   Next
Esri License Manager (old check)     IMS Service