ArcGIS Monitor Blog

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Other Boards in This Place

Latest Activity

(11 Posts)
Esri Contributor

Out of the box, ArcGIS Monitor comes equipped with some excellent general purpose counters that can be useful for maintaining your Enterprise GIS. But what happens when you want to monitor something that's not covered by any of the general purpose counters? Your first port of call may be to check the ArcGIS Monitor Gallery. Here you'll find some more specialized extensions that can be plugged straight into your Monitor deployment in a few simple steps. However if you can't find what you're looking for there, then your next step may be to start thinking about developing your own extension.

I recently found myself at this juncture, and when I went looking for documentation on writing extensions for ArcGIS Monitor - I discovered there wasn't much to be found. No matter though, I was just going to have to figure it out for myself. As a starting point I downloaded a few extensions and started reading through their code contained get a feel for how they work. What follows is a summary of my learnings from subsequent analysis and experimentation, for the purposes of this article I'm assuming that you have at least basic familiarity with node.JS development. 

File Structure of an ArcGIS Monitor extension

If you've imported an ArcGIS Monitor extension before, you may have noticed that what you're importing is a zip file containing at least

  • A folder that matches the intended name of the extension
  •  An index.js file within the named folder, that contains code to be executed by the ArcGIS Monitor service in a node.JS runtime

Often there will also be additional files included within this structure, this may include

  • A node_modules sub-directory containing node.JS modules required code used in the extension
  • Powershell scripts or windows executables to be executed by the index.js code
  • A testCmd.js which can be used during development to test the behaviour of the extension code without going through the process of loading the extension into ArcGIS Monitor

Out of all the possible files that may make up an ArcGIS Monitor extension, the named folder containing the index.js are our essential components. If we want to write our own extension for Monitor, our chief concern should be what goes into this index.js file, and how ArcGIS Monitor interacts with this code. This file follows a specific structure which allows the ArcGIS Monitor service to feed information into the script and run the code.

Extensions Inputs

First of all we have module.exports.inputs which is a JavaScript object defining the information we expect the user to provide when configuring a counter using our extension. This will shape the UI presented ot the user when configuring a counter using your extension. Each individual input is an object that needs to have at least a 'type' property, and can optionally have a 'value' and 'help' property. The type property will determine the UI control presented to the user in which to provide their input. The value property provides allows a default value to be set within the UI control presented to the user. And the 'help' property allows us to provide context sensitive help to the user, explaining what information they are expected to provide for each input.

As an example, I created an extension for ArcGIS Monitor that checks how many creator and view user type licenses are available in a 10.7.x/10.8.x Portal. The use-case for such an extensions would be to allow for an alert to be raised when we're starting to run out of either Creator or Viewer usertypes, so you as an administrator go look at freeing up inactive users or authorise additional licenses.

For our extension to interact with the Portal, it's going to need two key pieces of information:

  • The URL of the Portal; and
  • Credentials to facilitate authenticated access to the Portal
module.exports.inputs = {
portalUrl: {
type: 'string',
value: '<< >>',
help: 'Portal URL'
adminCredentials: {
type: 'credentialMap',
value: '<< portaladmin >>',
help: 'Portal Administrator credentials'
min_resolution: {
type: 'minimum_resolution',
value: 300

When loaded by ArcGIS Monitor this code will provide a field in which the user can enter a string of text specifying the Portal URL to connect to, along with the ability to add and/or select credentials saved with ArcGIS Monitor Administrator to for the purpose of authenticating with the Portal. The third input here 'min_resolution' is the minimum allowable sampling interval in seconds, which controls what options will be available to the user in the Sample Interval dropdown.

For more information on what types of inputs are available for ArcGIS Monitor extensions to use, you may be interested to check out my quick reference on ArcGIS Monitor Extension Input Types

Execute and Extension Functions

In the index.js script we need to export a function named execute that will server as an entry-point for the ArcGIS Monitor Service to run your extension's code. In the examples from the ArcGIS Monitor Gallery, the execute function makes use of the q library to return the Extension function as deferred promise. Given that the q library is no longer maintained and the Node runtime that ships in the current version of ArcGIS Monitor supports async/await language features that can be used to much the same effect - I chose to drop use of the q library in favour of modern syntax and more readable code. This involved making Extension an async function, and having the execute function return the promise implicly created by invoking the async Extension function. Techincally, this approach means the promise that gets returned the ArcGIS Monitor Service lacks the publicly accessible resolve/reject methods that would otherwise come with a q defferred - but in my testing this did not appear to have any impact on functionality or performance.

module.exports.execute = function (inputOptions) {
return Extension(inputOptions);

async function Extension(options) {

/* Here the Extension function will gather metrics to report back to Monitor Service */

var results = []; // Array of result to report back to the Monitor Service

//Each item in the result array will be an object containing 'name' and 'value' properties
results.push({name: "<metric name>", value: <metric value>}); 'value
//The monitor service expects the exentsion to report an exit code - in the event of an error, exit code should be non-zero
results.push({name: "Code", value: 0});
// Return the array containing the results
return results;

The Extension function called by execute is the one that's responsible for performing the business logic of the extension - that is to say it gathers whatever metrics or information we're interested in, and reports this back to the ArcGIS Monitor Service. The way in which you gather the information to report back can vary - in my Portal User Licenses example (attached at the end of this post), this was done in JavaScript using the axios http library to make REST API calls to the Portal. However other examples in the ArcGIS Monitor Gallery can also be seen using other techniques such as calling powershell and exe files and capturing the information they return.

Either way, once your script has gathered the metrics your extension is reporting on, this information needs to be formatted in a particular way so that it can be interpreted by the Monitor Service. We do this using an array of objects, where each metric is represented by a separate object, and each object has a 'name' and 'value' property. The name property defines the name of the counter as it will appear in ArcGIS Monitor Administrator, and the value property represents the data associated with your counter.

Finally, once we have the information formatted correctly this needs to be reported back to the Monitor Service by resolving the Extension promise. If using a q.deffered you would invoke the defferred's .resolve() method, however if like me you make Extension an async function - simply returning from the function will resolve the promise.

That's about all you need to know to get started with writing extensions for ArcGIS Monitor. If you want to dive deeper into the topic, check out the complete code for my example Portal User License monitoring extension attached below, and stop the ArcGIS Monitor Gallery for more examples. 

3 2 2,717
Esri Contributor

Esri User Conference 2020 has many virtual sessions across hundreds of topics. Below is a focused agenda to help you navigate your way to ArcGIS Monitor activities.


**Note: Please registeras all-access attendee to watch sessions and participate in the virtual expo at Esri UC 2020!**


Join us LIVE on Tuesday, July 14, at 8:40 am PDT 

ArcGIS Monitor: An Introduction technical workshop

Session ID: 10337

ArcGIS Enterprise administrators require effective monitoring solutions to meet the growing demand for feature-rich, highly available and performing ArcGIS solutions. In this session, you will learn to configure and diagnose the root causes of typical cases, e.g. performance, uptime and infrastructure problems using ArcGIS Monitor.

Who should attend this session?

GIS Managers, GIS Administrators, IT Managers, IT Administrators, Users with enterprise implementations



Virtual Showcase


Monday, July 13           12:05 PM–3:50 PM PDT

Tuesday, July 14           7:30 AM–9:40 AM and 11:10 AM–3:50 PM PDT

Wednesday, July 15     7:30 AM–9:40 AM and 11:10 AM–3:50 PM PDT


For ArcGIS Monitor questions and demos visit Booth ID: SH-19-01 to Chat or Schedule a Meeting with a product expert. (Located in the ArcGIS Enterprise area)



ArcGIS Monitor Resources:



“See” you at UC!

0 4 632
Esri Contributor

Recording from 2020 (virtual) Developer Summit is now available!

ArcGIS administrators require effective monitoring solutions to meet the growing demand for feature-rich, highly available and performing ArcGIS solutions. Hear from Andrew Sakowicz and Evan Mosby on how to install, configure, and diagnose the root causes of typical cases, e.g. performance, uptime and infrastructure problems.

0 0 343
Esri Contributor

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.

1 0 500
Esri Contributor

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.

2 0 609
Esri Contributor

Are you attending the Esri Partner Conference and Developer Summit in Palm Springs, CA next week? Stop by the ArcGIS Monitor stations inside ArcGIS Enterprise area at the expo. Our experts are available to demonstrate the product's capabilities and how your organization can benefit from using ArcGIS Monitor. 

Don't forget to attend the ArcGIS Monitor: An Introduction technical sessions to learn more. 

  • Thursday, March 4th at 2.30 PM (Catalina/Madera room)
  • Friday, March 5th at 1.00 PM (Mesquite C)

0 0 321
Esri Contributor

ArcGIS Monitor is a tool uniquely tailored to monitor the health of your ArcGIS implementations. In its latest release, it includes new Status page, Root Cause Analysis capabilities, and targeted reports for ArcGIS Server/Portal. New log counters and an API are also included. ArcGIS Monitor 10.7 makes you more productive.

Here’s what you can do:


Status summary

Quickly view the health status of your Enterprise GIS, Infrastructure, databases, and web Urls.

Explore Demo Site > Home tab


View Root Cause Analysis reports

Identify the sources of alerts and downstream impacts of the alert conditions for each 10 minute interval. Reduce investigation time of an alert or failure along with related downstream alerts and failures.

Explore Demo Site > RCA tab



Quickly parse log-severe, and log warning entries

With one click from the Alerts page, get detailed severe or warning entries for ArcGIS Server and Portal logs for the alert time. The more machines you have, the more time you will save investigating logs.

Explore Demo Site > Alerts tab



Run usage reports for ArcGIS Server and Portal

View unused services, and throughput (Tr/Sec), busy time per transaction (Sec), Log-Severe entries, and Log-Warnings for services. Quickly identify demanding services and they are logging errors.

 Explore Demo Site > Reports


Use API to extract alerts and availability stats

Get a standardized json output with info on alerts and availability statistics that can be integrated with other applications.

 Explore Demo Site > API

0 0 1,231
Esri Contributor

ArcGIS Monitor 10.6.1 includes new features and enhancements to make you more productive. Here’s what you can do:


Alerts filtering with links

Quickly filter and sort open or closed alerts with links to charts, statistics, and in some cases log details, or the source url. With one click, you can access severe or warning log entries for ArcGIS Server.

Explore Demo Site > Alerts tab

View current status icons

Use high-level status icons to quickly communicate collection status for managers. A count of healthy and unhealthy collections and count of alerts also help summarize the status more efficiently.

Explore Demo Site > Home tab

View availability status icons

Use high-level icons to quickly communicate the count of collections where availability is less than 99%. This allows administrators to focus on areas where availability was lowest for a time range.

Explore Demo Site > Availability tab

Monitor ArcGIS GeoAnalytics Server

When using GeoAnalytics Server, view new counters including status, cores, and memory for Workers in the GeoAnalytics tab.

View Health Check counters

Quickly check the Health Check counter for a site obtained directly from the ArcGIS REST API. A Health Check counter was added for both ArcGIS and Portal counter types in the Categories > ArcGIS report. A value of zero indicates the site level url is healthy and a value of 1 indicates the site is unhealthy. The Health Check counter is separate from ArcGIS Server logs. A site url may be healthy but have service level errors in the logs.

Use Windows authentication for ArcGIS, Portal, and Http counter types

Conveniently use credentials of the Windows administrative users in the ArcGIS Server built-in store or Active Directory to authenticate for ArcGIS, Portal, and Http in both federated and non-federated environments. Secured ArcGIS Server services requiring a token can also use Windows authentication if the Windows user that is running the ArcGIS Monitor Service has authorization to access the target site or service. Either ArcGIS Server authentication or Web Tier authentication can be configured.

View International dates and number formats

Internationalization support was added for date, time, and number formats to improve the usability for international environments. Unicode support was added for the installation, configuration, and data viewing of non-English usernames, passwords, labels, and input text.

Lastly, 6 new videos are available for ArcGIS Monitor 10.6.1:


  1. ArcGIS Monitor Demo for Managers
  2. ArcGIS Monitor Demo for Administrators
  3. Understanding Availability
  4. Add Portal
  5. Add ArcGIS Server
  6. Add Http

Questions? Comment below and we'll get back to you soon!

2 10 3,577
Esri Contributor

Esri is excited to announce the availability of two new services packages for the newly released ArcGIS Monitor: ArcGIS Monitor Jumpstart and ArcGIS Monitor 20-Hour Remote Consulting Services. While ArcGIS Monitor can be installed and configured on your own, these services packages support you through the install, configure and/or support phases of your implementation. 


ArcGIS Monitor Jumpstart

The ArcGIS Monitor Jumpstart services package provides remote installation and configuration support (a standard implementation using the default monitoring counters), followed by 2 days onsite for configuration review and ArcGIS Monitor knowledge transfer by 1 Esri senior consultant. ArcGIS Monitor includes default counter types such as System, Process, ArcGIS Server, Portal, Database, Http, Remote Desktop Protocol (RDP), and Amazon servers.


The ArcGIS Monitor Jumpstart Services Package provides the following benefits:

  •     Reduces the time it takes to install and configure ArcGIS Monitor software.
  •     Increase productivity and effectiveness through technology transfer of common ArcGIS Monitor topics.
  •     Reduce the time it takes to implement or become proficient with ArcGIS Monitor.
  •     Timely access to Esri Professional Services experts with comprehensive knowledge of Esri products and solutions.
  •     Maximizes GIS investments through more effective system operation and reduced administration costs.


ArcGIS Monitor 20 Hr Remote Consulting

The ArcGIS Monitor remote services package provides up to 20 hours of remote consulting support to be provided by an Esri senior consultant to interpret ArcGIS Monitor results, review a customer’s ArcGIS Monitor configuration and implementation, make recommendations for adjusting configuration settings and support for deploying custom monitoring agents and extensions.


The ArcGIS Monitor 20 Hr Remote Consulting Services Packages provides the following benefits:

  •     Timely access to Esri Professional Services experts with comprehensive knowledge of Esri products and solutions.
  •     Maximizes GIS investments through more effective system operation and reduced administration costs.


For more information about ArcGIS Monitor and/or these service packages please reach out to your Esri account manager or international distributor.

0 0 605
Esri Contributor

A Proactive Approach to GIS Implementations


Williams, an energy infrastructure company, owns and operates midstream gathering and processing assets as well as interstate natural gas pipelines. Founded in 1908, Williams employs more than 5,600 people. With headquarters in Tulsa, Oklahoma, Williams also operates major offices in Houston, Texas; Pittsburgh, Pennsylvania; Oklahoma City; and Salt Lake City, Utah.


The geographic information system (GIS) environment at Williams includes a Citrix environment with an average of 120 ArcGIS Desktop users and supports 63 development, QA, and production servers (mostly virtual). The clustered ArcGIS Server environment hosts services and 164 maps. A federated ArcGIS portal runs 238 services, 199 maps, 30 feature services, and accommodates 1,800 users. With so many workers depending on GIS maps and services, Williams needed to be able to proactively monitor its implementation.

"Anytime a web map or map service wasn't working correctly, we would have to research what's causing the issue," said Steve McCarthy, a systems architect at Williams. "We'd start by looking at the web app, then maybe end up having to dig into the code to figure out what's not working right. This could take several hours or days."


McCarthy and his team would have to take time away from projects to determine the cause of the problem—whether it be a broken link, a bad index, or an underpowered service. He and his team needed to be able to identify problems or potential problems and reliably run multiple applications in their GIS environment. This would allow qualified staff to focus on creating new applications or fine-tuning current applications rather than troubleshooting.


Williams implemented ArcGIS Monitor, a tool uniquely tailored to monitor the health of ArcGIS implementations. ArcGIS Monitor provides insightful information about system usage and performance via noninvasive monitoring of enterprise GIS and IT infrastructure including databases, networks, and GIS software. The solution provides timely detection of potential and existing system infrastructure and operational problems to facilitate a rapid resolution. It also provides actionable reports and quantifiable metrics to improve communications among GIS and IT staff, business owners, and senior management.

Since implementing ArcGIS Monitor, Williams has reduced the amount of time spent on troubleshooting and response. The company has also been able to save the cost of extra resources by making those purchases only when proved to be necessary.


"ArcGIS Monitor provides reports that are very helpful," McCarthy said. "It lets us see where there is heavy traffic. The Excel reports show` me where I might have issues such as broken links or data change by hour or over a period of time."


With a better grasp of available resources, McCarthy and his team can quickly determine how much growing room they have and when they may need to add resources such as extra servers, storage, memory, or CPUs. His team uses ArcGIS Monitor reports to justify the use of resources and the need for more.


McCarthy can fine-tune the ArcGIS Server environment at Williams to cater to whatever services are popular. He uses feedback from ArcGIS Monitor to increase resources based on heavy activity or decrease them based on low activity. While McCarthy elected to receive alerts from ArcGIS Monitor when the server reaches 75 percent capacity, users can set alerts to any desired size or percentage of capacity. ArcGIS Monitor also provides hourly reports on all systems. The team at Williams makes these published reports available to developers and users who need relevant information.


"We've gone from responding to issues to proactive, high-performance tuning," McCarthy said. "Now, we don't go buy extra resources unless we can justify it. In the past, we would only be able to assume we need more memory or more servers. ArcGIS Monitor helps build confidence in our GIS because we have very little downtime."


For more information contact Esri at

0 0 707