ArcGIS Monitor system requirements

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

Note:

ArcGIS Monitor Agent requires the sysstat package for monitoring.

Linux operating system requirements

The following 64-bit operating systems 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.

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

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

The software should not be installed 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 8	Update 9
Red Hat Enterprise Linux Server 9	Update 3
Ubuntu Server 22.04 LTS	22.04.4
Ubuntu Server 20.04 LTS	20.04.6
Oracle Linux 8	Update 9
Oracle Linux 9	Update 3

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

Caution:

To run the ArcGIS Software Authorization wizard using the operating system graphical user interface (GUI), the X Window System package group is required.

SELinux support

The Security-Enhanced Linux (SELinux) module is supported on machines running ArcGIS Monitor. Because the default policy of SELinux may prevent Monitor from reaching internal components such as the configuration store, administrators may need to modify the SELinux policy. To do so, temporarily set the SELinux policy mode to permissive. This will record the violations of policy, such as actions taken by Monitor to access internal directories, but will allow them to occur. Administrators can note these violations by Monitor and modify the SELinux policy configuration to allow them before resetting the policy mode to enforced.

Hardware requirements

For ArcGIS Monitor Server, a minimum of 2 CPU cores and 4 GB of RAM are required.

For ArcGIS Monitor Agent, a minimum of 1 CPU core and 2 GB of RAM are required.

Note:

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

Temporary space requirements

Resources are extracted to a directory created in the system /tmp directory by default. This directory must have read, write, and execute permissions enabled. Approximately 250 MB of temporary disk space is required during the installation of this product. This temporary disk use is removed at the end of the installation. If the required space is not available in the /tmp directory, the setup program reports an error indicating this problem. Optionally, you can 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 is preconfigured with a self-signed certificate that allows you to perform initial testing and verify that the installation was successful. You must 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

Amazon Elastic Compute Cloud (EC2) instances can be monitored by installing Monitor Agent on each EC2 instance and registering the Monitor Agent instances with Monitor Server. Amazon Relational Database Service (RDS) resources can be monitored by registering the AWS account for monitoring and tagging each RDS resource in AWS for monitoring.

Note:

Individual databases hosted in RDS must be registered separately as database components; their metrics can't 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
• Mozilla Firefox
• Microsoft Edge
• Safari

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. It is recommended that you 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 the creation of the ArcGIS Monitor Information Model and the maintenance of its schema.

Supported database software	Latest version tested	Privileges
PostgreSQL (64 bit)	16.3	LOGIN NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE NOREPLICATION
	15.7
	14.12
	13.15

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 agm 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 agm WITH OWNER=agm;

GRANT ALL ON DATABASE agm TO agm;

Configure the database to allow 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 to the database cluster, alter the PostgreSQL pg_hba.conf configuration file. The entries you place in the pg_hba.conf file vary depending on your organization's security policies and configurations.

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

1. Make a backup copy of the pg_hba.conf file before you alter it.
2. Open the pg_hba.conf file in a text editor.
3. 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 agm, 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    agm    agm    1.2.3.4/32    scram-sha-256

   For more information, refer to the PostgreSQL documentation.

4. Reload the server configuration settings using a PostgreSQL function such as pg_ctl reload or SELECT pg_reload_conf().

Database hardware requirements

A minimum of 2 CPU cores, 4 GB of RAM, and 100 GB of storage are required.

Database storage requirements for Monitor vary depending on the number of components monitored and your organization's data retention policy. Use ArcGIS web services as the primary driver for database storage requirements since 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 provides enough storage space to monitor the implementation for a period of one year. If the implementation contains more ArcGIS web services, you must 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.

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.