ArcGIS Monitor system requirements

Before installing ArcGIS Monitor, review the software and hardware requirements to run it.

Note:

Monitor requires the Microsoft Visual C++ 2015-2022 Redistributable (x64) package for Visual Studio, minimum version 14.38.33130. Obtain the Visual C++ Redistributable package from the Microsoft site.

If the required Visual C++ Redistributable package is not installed, running the Monitor Setup.exe file will install it. Running the Monitor setup.msi file does not install the Visual C++ Redistributable (x64) package. To run the Monitor setup.msi file, you must install the Visual C++ Redistributable (x64) package first.

Monitor requires the optional Windows VBScript feature to be enabled. The installers use VBScript-based custom actions and fail with error 2738 when VBScript is disabled or unavailable. You can enable VBScript temporarily for installation and disable it afterward if required by your organization's security policy.

Microsoft Windows operating system requirements

The 64-bit operating systems listed below satisfy the minimum operating system requirements. Support is not provided for 32-bit operating systems; the setup only proceeds if the operating system is 64 bit.

Supported operating system	Latest update or service pack tested
Windows Server 2025 Standard and Datacenter	March 2026 update
Windows Server 2022 Standard and Datacenter	March 2026 update
Windows Server 2019 Standard and Datacenter	March 2026 update

Development environments

The following development environment is supported:

Supported operating system	Latest update or service pack tested
Windows 11 Pro and Enterprise	March 2026 update

Note:

Future updates or service packs on the operating system (OS) version are supported unless otherwise stated. The OS version and updates must also be supported by the OS provider.
Monitor is only supported on 64-bit CPUs with x86-64 architecture.
The Desktop Experience option is required on all versions of Windows Server.
Windows 11 is supported for basic testing and application development use only.
Machines with an underscore (_) in their names are not supported. Several widely used internet host name specifications have designated the underscore character as nonstandard. Although Microsoft Windows allows you to use the underscore in a machine name, it can still cause problems when you interact with other servers and platforms. For this reason, the installation will not proceed on servers that have an underscore in the host name.
You cannot install on domain controllers. Installing on a domain controller may adversely affect functionality.

Note:

ArcGIS Monitor Agent requires the sysstat package for monitoring.

Linux operating system requirements

The 64-bit operating systems listed below satisfy the minimum operating system (OS) requirements. Support is not provided for 32-bit operating systems; the setup only proceeds if the operating system is 64 bit.

Monitor is only supported on Linux x86_64 with supported Linux releases. CPUs must adhere to the x86_64 architecture (64 bit).

Machines with an underscore (_) in the name are not supported. The setup does not proceed if an underscore is detected in the machine name.

Do not install the software on an OS (binary) that has been modified. Esri does not provide support for products installed on a developer's release of an operating system.

Supported operating system	Latest update or service pack tested
Red Hat Enterprise Linux Server 9	Update 7
Red Hat Enterprise Linux Server 8	Update 10
Ubuntu Server 24.04 LTS	24.04.4
Ubuntu Server 22.04 LTS	22.04.5

Past and future updates or service packs for these OS versions are supported unless otherwise stated. The OS version and updates must also be supported by the OS provider.

SELinux support

The Security-Enhanced Linux (SELinux) module is supported on machines running ArcGIS Monitor. The default SELinux policy may prevent Monitor from reaching internal components such as the configuration store. To modify the policy, administrators can temporarily set SELinux mode to permissive. This records policy violations, such as Monitor attempts to access internal directories, but allows operations to continue. Administrators can review these violations and update the SELinux policy configuration before resetting the mode to enforced.

Hardware requirements

ArcGIS Monitor Server requires a minimum of 2 CPU cores and 4 GB of RAM.

ArcGIS Monitor Agent requires a minimum of 1 CPU core and 2 GB of RAM.

Note:

Depending on your organization's needs, and performance and capacity expectations, the implementation may require more cores or RAM.

Temporary space requirements

By default, setup extracts resources to a directory in /tmp. This directory must allow read, write, and execute permissions. Installation requires approximately 250 MB of temporary disk space. Setup removes this temporary disk use at the end of installation. If the required space is unavailable in /tmp, setup reports an error. Optionally, specify an alternate temporary location by setting the TMPDIR environment variable.

Default file permissions

The ArcGIS Monitor account is the owner of the Monitor installation directory. For security reasons, all permission types (read, write, and execute) for all other users and groups are turned off by default.

Firewall settings

Monitor communicates on specific ports. Open these ports on your firewall before installing the software.

Learn more about ports used by Monitor

SSL certificates

Monitor includes a self-signed certificate to help you with initial testing and installation verification. Request a certificate from a trusted certificate authority (CA) and configure Monitor Server to use it. This can be a domain certificate issued by your organization or a CA-signed certificate.

Cloud platforms

Monitor can monitor cloud resources and ArcGIS software installed in a cloud environment. Review the section for your cloud environment for more information.

Amazon Web Services

Monitor can monitor Amazon Elastic Compute Cloud (EC2) instances when Monitor Agent is installed on each EC2 instance and each agent is registered with Monitor Server. Monitor can monitor Amazon Relational Database Service (RDS) resources when the Amazon Web Services (AWS) account is registered for monitoring and each RDS resource is tagged for monitoring.

Note:

Individual databases hosted in RDS must be registered separately as database components; their metrics cannot be acquired through CloudWatch.

For monitoring to function in AWS, Monitor requires an AWS Identity and Access Management (IAM) user with specific permissions for monitoring, an access key ID, and a secret key.

Learn more about preparing AWS for monitoring

Supported web browsers

Monitor supports the following web browsers:

Google Chrome
Microsoft Edge
Mozilla Firefox

Note:

The web browser version must be supported by the web browser's provider.

Required database repository

The Monitor database contains the ArcGIS Monitor Information Model and must be hosted in a PostgreSQL database. Install a dedicated database instance, or configure an existing database instance, for the Monitor repository before installing Monitor.

Note:

Client drivers are included with the Monitor software.

You must create a dedicated database and user for Monitor. Once Monitor Server is connected to the database, it manages creation and schema maintenance of the ArcGIS Monitor Information Model.

Supported database software	Latest version tested	Privileges
PostgreSQL (64 bit)	17.5	LOGIN NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION
	16.9
	15.13
	14.18

Note:

The specific versions listed above are the minimum minor versions supported and certified for each supported major release of PostgreSQL. Newer minor versions are also supported. The PostgreSQL version and updates must be supported by the PostgreSQL Global Development Group.

The following is an example of SQL commands to run as the postgres user to create a database user named agm and a database named agmdb for Monitor Server. Replace <password> in the example below with the password that you want to assign to the database user.

CREATE USER agm WITH PASSWORD '<password>'
  LOGIN
  NOSUPERUSER
  INHERIT
  NOCREATEDB
  NOCREATEROLE
  NOREPLICATION;

CREATE DATABASE agmdb WITH OWNER=agm;

GRANT ALL ON DATABASE agmdb TO agm;

Configure the database to allow remote connections

By default, only clients running on the same machine as the PostgreSQL database cluster can connect to it. To allow remote clients to connect, alter the PostgreSQL pg_hba.conf configuration file. Entries in pg_hba.conf vary based on your organization's security policies and configurations.

To allow remote connections from clients to the PostgreSQL server, complete the following steps:

Make a backup copy of the pg_hba.conf file before you alter it.
Open the pg_hba.conf file in a text editor.
Add a record to the pg_hba.conf file using the following syntax:
```
# TYPE    DATABASE                   USER                   ADDRESS                          METHOD
host      <monitor_database_name>    <database_username>    <monitor_server_ip>/<ip_mask>    <authentication_method>
```
For example, if the Monitor database name is agmdb, the database username is agm, the IP address of the machine on which ArcGIS Monitor Server will be installed is 1.2.3.4 with an IP mask of 32, and the authentication method is scram-sha-256, the record would be added as follows:
```
host    agmdb    agm    1.2.3.4/32    scram-sha-256
```
For more information, refer to the PostgreSQL documentation.
Reload the server configuration settings using a PostgreSQL function such as pg_ctl reload or SELECT pg_reload_conf().

Database hardware requirements

The database requires a minimum of 2 CPU cores, 4 GB of RAM, and 100 GB of storage.

Monitor database storage requirements vary based on the number of components monitored and your organization's data retention policy. Use ArcGIS web services as the primary driver of database storage requirements because they consume the most disk space. Allocate at least 100 GB of storage for enterprise GIS implementations with up to 1,000 ArcGIS web services. This amount provides enough storage to monitor the implementation for one year. If the implementation contains more than 1,000 ArcGIS web services, allocate an additional 100 GB of disk space for every 1,000 ArcGIS web services.

Note:

Depending on your organization's needs, and performance and capacity expectations, the database repository may require more cores, RAM, or storage.

ArcGIS Web Adaptor

Web Adaptor provides a connection between your enterprise web server and Monitor. It allows you to specify the port, address, and authentication settings for incoming requests. To configure Web Adaptor with Monitor, a dedicated instance of ArcGIS Web Adaptor 12.1 is required.

Learn more about installing and configuring Web Adaptor with Monitor

Monitoring requirements

All components supported by Monitor have individual requirements for monitoring. Refer to the prerequisites section of the component type that you want to register for more information.