Skip navigation
All Places > ArcGIS Monitor > Blog > 2019 > April

Multiple metrics are used to define the health of your enterprise GIS. ArcGIS Monitor was created for administrators to quickly identify and deal with problems with ArcGIS, whether they are in the software or elsewhere in the stack. To properly diagnose if your GIS systems are healthy, administrators need to be aware of when alerts happen and their criticality as well as understand their root cause.



When the system is not healthy, there might several hundreds of alerts in your dashboard. To help better analyze the alerts, ArcGIS Monitor divides them into three categories – critical, warning and info. Addressing critical alerts is top priority for every administrator as they impact availability and the smooth running of your enterprise GIS. Warning alerts indicate resources running low – memory, disk, CPU or network bandwidth. Info alerts are logs that are informational for the administrator.


There are several options to investigate errors – you can view when the error occurred, parse log entries for that time or click on the included log errors links and admin URLs to check site details.


Root Cause Analysis

While administrators need to know when alerts happen, it is also essential that they understand the root cause, the source and the impact, of a problem. For example, an outage of an ArcGIS Data Store impacts all of the tiers above it. The source, in this case, would be the ADS and the impact would be ArcGIS Server and portal sites affected by the outage.


One of the common root causes is system overload. When the system receives loads exceeding its capacity, this results in excessive resource utilization such as 100% CPU, zero free memory, or zero idle disk. This, in turn, lowers performance, causes time outs and impacts overall stability of the enterprise implementation. 


Another common root cause is system bottlenecks, which impact performance and stability while the resource utilization is low. Bottlenecks manifest during increased user load such as the above case.


Lastly, unstable infrastructure is another cause to look for. Restarting services, changing permissions, expired passwords or virtualization overallocation can impact system stability. Examples include unexpected processes consuming memory, CPU usage spikes, stopped ArcGIS Server services, reboot conditions and databases not running.


ArcGIS Monitor provides reports that speak the language of administrators, enabling easy diagnosis of the health of your enterprise GIS, and manage GIS hardware and infrastructure needs. Monitor shows you where the issues are through quantifiable key performance indicators and metrics.


This video demonstrates the above mentioned key features.

For GIS Managers, maintaining the health of the GIS implementations is critical to keep it running smoothly. Tracking system availability, usage and performance, and proactively managing outages while providing the level of service as expected from an enterprise GIS is a given.


ArcGIS Monitor is specifically designed to monitor ArcGIS implementations by providing timely and insightful metrics, thereby maximizing your GIS investment. Monitor allows you to proactively assess and optimize hardware and GIS software resources to determine growth and justify use of current resources as well as need for additional resources.


System Availability

Availability is the amount of uptime during a given time span—such as a month or a year—and is expressed as a percentage of time. This number, for example 99.9% available, is very important to know for Service Level Agreement (SLA) in your organization.



Managers would also need to look at the usage patterns of your ArcGIS enterprise deployment. You can take advantage of usage statistics such as load balancer and ArcGIS Server transactions to answer what services and data is in demand by customers. These metrics help managers in capacity planning and understanding applications or services usage at different time periods. 



Managers can review reports that quantify system resource utilization and detect unused services that are consuming resources unnecessarily. For example, busy time per transaction (sec) metric help pinpoint specific service name that is consuming a lot of CPU. These reports and metrics enable managers to optimize their enterprise GIS deployments.


This video demonstrates the above mentioned key features.