Konfigurieren eines Portal-Zählers in ArcGIS Monitor für eine ArcGIS Enterprise-Bereitstellung mit hoher Verfügbarkeit

Zusammenfassung

In a highly-available ArcGIS Enterprise deployment, there are some special considerations for how to set up a portal counter in ArcGIS Monitor. Setting up a portal counter for each individual portal machine in the highly-available Portal for ArcGIS site can cause instability in federated ArcGIS Server sites.

In particular, the machines of the hosting ArcGIS Server site have shown to experience instability when multiple portal counters are configured with the Status Federation alert.

Ursache

The Status Federation alert is included with the default alerts for ArcGIS Monitor's portal counter. If a Status Federation alert is configured, requests to check the validation status of the ArcGIS Data Stores in the hosting ArcGIS Server site occur.

Instability in federated ArcGIS Server sites can result when more than one of these Status Federation checks are performed simultaneously.

Vorgehensweise

It is strongly recommended to include only one portal counter that has the Status Federation alert configured. The Site URL for this counter should be a load-balancer URL.

If certain alerts are desired for each individual machine in the Portal site, additional portal counters can be configured for each individual portal machine. If you choose to create additional portal counters for each individual machine in the portal site, please consider the following:

• Do not include the Status Federation alert for these individual portal machine counters.
• Do not use the full list of default alerts for these individual portal machine portal counters, instead use alerts that are specific to the machine in question.

If additional portal counters are desired for each individual portal machine, there will be three portal counters:

• One counter for the portal site's load-balancer (WebContextURL)
• One counter for portal machine #1 (port 7443 URL)
• One counter for portal machine #2 (port 7443 URL)

In this pattern, omit alerts that should not be duplicated from the individual portal machines' counters, for example, Status Federation. Likewise, it can be beneficial to include any alerts that are applicable to an individual portal machine on the individual portal machine's counters, for example, Storage Available and Status Machine.