Deployment scenarios

ArcGIS Monitor is designed to be scalable; it can accommodate both small and large deployments. When you begin building your site, you may want to start small and install all the components on a single machine. As you expand your production site, or if your site adds more counters, you can change the configuration.

When designing a site, consider the number and frequency of counters, geographic location, and the industry to be monitored. The administrator should understand solution architecture, all software components, and dependent infrastructure and use this knowledge to choose and configure appropriate counters and extensions.

Centralized deployment

In this deployment, ArcGIS Monitor Administrator and the ArcGIS Monitor Server application (with MongoDB) are installed on the same machine. This is the preferred option if there's marginal network latency between ArcGIS Monitor Administrator and the target environment from which the counters are collecting data.

Distributed deployment

In this deployment, ArcGIS Monitor Administrator and the ArcGIS Monitor Server application (with MongoDB) are installed on different machines. This option should be used when there's significant network latency between ArcGIS Monitor Administrator and the target environment from which the counters are collecting data.