Overview settings

ArcGIS Enterprise Manager provides an active view of your organization where you can monitor recent log messages, available disk space for system managed data storage, and system and utility service pod status.

When you sign in to ArcGIS Enterprise Manager, the Overview page provides summaries of the current status of the system. On this page, you can view index status or reindex as needed, review and access logs, and check the status of system managed data storage.

Refresh interval

The refresh interval setting identifies the frequency at which information such as health and status for each resource type is pulled and cached. If a refresh interval is specified as 0, no information is collected and cached for that resource type.

From Overview settings, set the refresh interval for each functional area of this page. The following are the default interval values for each resource type:

  • Critical logs—0 minutes
  • System managed data stores—1 minute
  • System service pods—1 minute
  • Utility service pods—1 minute

After updating a refresh interval to increase or decrease the frequency at which the status is retrieved, click Save.

To update the refresh interval settings back to the default values, click the Reset all to default button and click Save.

Critical logs

In the Critical logs section, you can review the most recent logs, for example, those logged at the Severe level. Logs are displayed with a time stamp of when they occurred, along with severity level, a brief message, and the pod source from which the log originates. To view additional logs, details, and settings, click View all.

Index status

In the Index status section, you can verify that the index and index store counts of your organization's users, groups, and items are in sync. Following an upgrade, you may find that the index store values no longer match the index values. This indicates that the index store is out of date, and you must run a reindex.

An out of date index store will cause you to encounter issues when searching for content within your organization. Content that is missing when you search for it may be available elsewhere in your organization. You will still need to run a reindex for your organization to optimally function.

When values are out of sync, click the Reindex all button.

System managed data stores

In this section, you can view and validate the health status of system managed data stores.

The following are the system managed data store types:

  • Object store—Storage for uploaded and saved content, hosted tile and image layer caches, and geoprocessing output.
  • Relational store—Storage for hosted feature data and administrative items such as customization and configuration settings. Two relational stores are configured: a primary and a standby.
  • Spatiotemporal and index store—Storage for logs and indexes as well as hosted feature data.
    Note:

    Spatiotemporal-hosted feature layers are not supported at this release.

Next to each data store type, the health status for the pods is available. To refresh the status of the system storage, click Validate.

If the space of the relational store and spatiotemporal and index store reaches the threshold limit, the stores will enter read-only mode and not accept new data.

To determine the available storage or memory for each dedicated storage pod, click the data store type to expand it and see a summary. The memory size is predefined and cannot be scaled at this release.

Note:

Available storage and memory usage information is not available for cloud-native object stores. To help locate and manage storage on its dedicated platform, relevant information such as the service provider, defined region or storage domain, bucket or container name, and authentication type is available on this page.

The number of dedicated pods for each storage type is determined by the architecture profile chosen during deployment.

System and utility service pods

System and utility pods provide the underlying framework to support your organization's workflows to share items such as maps, apps, and scenes; publish GIS services; and generate statistics and monitoring tools. In both the system and the utility services sections, you can verify the number of pods allocated to support these resources and determine whether any are unexpectedly low or unhealthy.

To increase or decrease the number of pods for system and utility services, use the settings on the Service deployments page. You can reallocate resources for the services in these pods on the Services page.