Latest Contributions by AndrewSakowicz

There is a known performance issue in analysis when using metric name and repeated refresh calls in 2023.2 and older.  These issues are fixed in 2023.3.1 patch to be released on January 30.   Please install it and hopefully it will address your performance / PostgreSQL high CPU.  In the meantime, you can kill long running sessions using PG Admin and not use "offending" analysis until a fix.     ... View more

Please use Admin Utility for ArcGIS Monitor - Esri Community or AdminUtility - Overview (arcgis.com) ... View more

2023.2 does not have run now option, but the job will be executed daily ... View more

this is executed daily. ... View more

In short, no. You need to drop partitioned data as per below. ... View more

To clarify, ArcGIS Monitor admins don’t need to run manually the above maintenance. The autovacume and autoanalyze are sufficient.  You can check with the following sql: select relname,last_autovacuum, last_autoanalyze from pg_stat_user_tables where last_autoanalyze is not null In some cases, these default jobs might be interrupted (e.g. locks, see below) or not running.  In that case, a manual analyze (as above or using PGAdmin UI) might be required. Keep in mind, it will place a lock and interfere with data collections while it’s executing. For more information , see documentation. https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM For many installations, it is sufficient to let vacuuming be performed by the autovacuum daemon, which is described in Section 25.1.6. Autovacuum workers generally don't block other commands. If a process attempts to acquire a lock that conflicts with the SHARE UPDATE EXCLUSIVE lock held by autovacuum, lock acquisition will interrupt the autovacuum. Warning Regularly running commands that acquire locks conflicting with a SHARE UPDATE EXCLUSIVE lock (e.g., ANALYZE) can effectively prevent autovacuums from ever completing. ... View more

This issue will be addressed in upcoming ArcGIS Monitor 2023.3.1 patch.   ... View more

Note, individual service level stats are available in Excel report ... View more

@JoeGuziStarkCountyOH , To clarify, these stats are at service level.  We discuss how to interpret these metrics and other operations scenarios in ArcGIS Monitor: Operational Scenarios - Esri Videos: GIS, Events, ArcGIS Products & Industries, e.g.  Perhaps we can connect at the next conference.  Also, our Esri Professional Service can help as well.   ... View more

Please note, ArcGIS Monitor 2023 has simplified reporting of ArcGIS Instances usage: Instance Saturation Percent, Instances Used, Requests Received, see Metrics reference—ArcGIS Monitor | Documentation TRSum is equivalent to Requests Received SUM in excel report. Percentiles and potentially wait times will be included in the later releases.   ... View more

Thank you for the feedback.  We are working on this issue.  We hope to include this fix in upcoming 2023.3 or the 2024 release. ... View more

@IrisHadarStltd , to clarify, this utility does not build a json.  It simply imports ArcGIS Monitor internal implementation of analysis configuration (jsonb configuration field in analysis table).   This analysis configuration json is internal implementation and subject to change.  Note, analysis export/import supported feature will be available in 2024.  ... View more

@Pat_Gallagher .  Thank you for reporting this. This a known issue that will be addressed in 2023.3 ... View more