ArcGIS Monitor 2024.0 Release Notes

ArcGIS Monitor 2024.0 is a major release with several key new features, enhancements, and fixes.

ArcGIS Monitor 2024.0.1 is a cumulative maintenance release for the Server and Agent, addressing stability issues.

ArcGIS Monitor 2024.0.2 is a cumulative maintenance release for the Agent only, addressing stability issues.

• FEAT: Agent architecture has been changed from remote monitoring to local monitoring, requiring an Agent to be installed on each monitored host
• FEAT: Server and Agent now supports administrative CLI commands
• FEAT: Agent now discovers and advertises Components it can monitor to the user
• FEAT: Agents now support highly-available Portal for ArcGIS deployments by way of local Agents
• FEAT: Dataviews allow query expressions to be shared among Analyses
• FEAT: Components can now quickly be compared and sent to an Analysis via the Monitoring page
• ENH: Monitoring of AWS RDS has been converted from a Host to its own unique Component type, capturing its own unique attributes and metrics
• ENH: Agents monitoring of multi-machine ArcGIS Server sites is improved by way of local Agents
• ENH-000166576: Notifications now accepts email addresses longer than 64 characters
• ENH-000166052: Application redirects now supports query string parameters when loading the target page
• ENH-000159142: Users are now notified when software license becomes invalid
• ENH-000157670: Password reset now supports e-mailing user

• BUG-000158552: Storage metrics for some cloud based hosts would not collect properly
• BUG-000166461: Portal for ArcGIS users active metric would unexpectedly fluctuate slightly by one
• BUG-000162471: Secure Collection based feature services would sometimes present an error when adding to Portal for ArcGIS
• BUG-000167330: Analysis chart value axis could sometimes become hidden when date filtering was enabled
• BUG-000168693: The Statistic Axis Title (Y-axis label) does not display for serial charts for some component category fields in ArcGIS Monitor
• BUG-000165141: Linux host monitoring could fail when utilizing a non-standard SSH port. With the introduction of universal agents, use of SSH is unnecessary and has been removed
• BUG-000166855: Password changes for monitored database components would result in an error
• BUG-000165915: Analysis charts would unexpectedly not present data when enabling date filtering
• BUG-000158709: Analysis chart decimal format could be inconsistent
• BUG-000166082: Metrics configured to alerting off present a nominal status after upgrading
• BUG-000164648: Filtering a datetime column using the "is on" operator would filter on specific time, rather than the entire date
• BUG-000164605: Notifications could send emails for deleted Alerts
• BUG-000165954: ArcGIS Server discovery observers could intermittently return no services and delete the local inventory
• BUG-000165306: Portal for ArcGIS, Health Checks observer was mislabeled
• BUG-000161800: Collections expressions could fail using a where clause and related children resource
• BUG-000158965: Expression builder field value selectors do not populate for parent or child resources
• BUG-000158150: Host process contextual metrics included extraneous command line details which caused REST queries to fail
• BUG-000165258: ArcGIS Server service request rate metrics were miscalculated for intervals greater than one minute
• BUG-000165344: ArcGIS Server discover observer would fail when usage report names consisting of all numbers were present
• BUG-000165271: Changing a user's password would result in an error
• BUG-000157134: Initial admin account was unable to recover its password immediately following creation
• BUG-000162213: Certain AWS EC2 Cloudwatch metrics would not populate without a Cloudwatch agent. With the introduction of universal agents, AWS Cloudwatch is unnecessary for Host monitoring
• BUG-000162233: Component name field was empty for Collection feature service metric layer
• BUG-000158002: Windows Host components could not be registered if the password contained certain special characters. With the introduction of universal agents, Host monitoring now inherits the underlying ArcGIS Monitor account
• BUG-000165281: Re-registering Portal for ArcGIS can sometimes fail
• BUG-000168440: The ArcGIS Monitor stacked bar charts do not stack properly when a filter is applied to the Data Metrics section
• BUG-000165275: Reset password workflow would cause a loop where the password could not be changed
• BUG-000169641: "Connectivity - arcgis_portal_discover" metric could return no data after restoring the default agent

2024.0.1

• BUG-000170617: When registering a Portal for ArcGIS component, the authentication token would sometimes not properly generate
• BUG-000170456: When the ArcGIS Monitor database became unavailable, Agents would fully disconnect themselves
• BUG-000170828: When an empty analysis view existed, the database would appear disconnected after upgrading to 2024.0
• BUG-000170827: If a notification existed with one or more contacts attached, the ArcGIS Monitor database would appear disconnected after upgrading to 2024.0
• BUG-000170847: ArcGIS Server service components would not appear after upgrading to 2024.0

2024.0.2

• BUG-000171574: ArcGIS GeoEvent Server would fail to register for monitoring

• agent_id field has been removed from Components, Metrics, and Observer tables and replaced with a many-to-many relationship between Agents and Components, to support multi-machine ArcGIS Server sites and highly available Portal for ArcGIS
• AWS EC2 and EBS volume monitoring through AWS integration has been replaced by the local Agent architecture to provide more robust monitoring capability