Latest Contributions by EsriEvan

Hi everyone   Thanks for reporting this. Dev team is aware the core ArcGIS service metrics are all reporting zeros, which in turn affects calculated metrics such as Instance Saturation. The root cause and will have the fix included into a 2024.1.1 patch to address these 2024.1 issues. This patch is being scheduled now and will be out as quickly as we can. ... View more

Hi folks, Thank you all for reporting this. The team has been triaging it this morning and believe this issue is presenting specifically for ArcGIS Data Stores which were upgraded (for instance 11.1 ->11.4). Non-upgraded Data Stores do not seem to be affected. The team is working to address this and determine how best to deliver the fix. Thanks! ... View more

Hello Iris, Details regarding monitoring SQL Server, including metrics, can be found in the link below. Note that for database monitoring, no local agent is required. Any Agent can remotely monitor a database, which is helpful for SaaS databases. A bug was fixed at 2024.0.2 related to Azure SQL Server monitoring (also linked below).   Register SQL Server databases—ArcGIS Monitor | Documentation BUG-000164409 for ArcGIS Monitor   Thanks ... View more

Hello folks, the development team is aware of this issue and is working to include it in a 2024.0.1 patch (to be released as soon as possible). The cause has to do with how Portal chooses to redirect requests from certain hosts (IP vs FQDN vs hostname) and how those redirects are handled within the AGM Agent. Dev team is unaware of a workaround at this time.  ... View more

Hi Tristan, What you shared sounds like a scenario that affects some users upgrading to 2023.3.1, where, due to the size of the DB, upgrade's data model migrations take longer than expected, which leaves the server in a state where the user cannot connect until the migrations complete. Dev team is working on providing feedback in these cases so we can be more confident during upgrades.  From your explanation, I think "toggling" the config-store is just disconnecting from the registered DB. The original config-store is probably fine, it's just triggering that data model upgrade and it's taking a while. If you contact support, they have some quick steps to validate this is the scenario and accelerate the upgrade. Thanks, Evan ... View more

If you are running 2023.3, there is a known issue which requires the database maintenance job to be run manually via Administration > Database > Run. This sounds like that issue. It will be addressed in the 2023.3.1 patch coming soon. ... View more

Hi @DanMallett , I am not familiar with nginx configuration, but it seems the URL provided may be mismatching the protocol with the port. HTTP --> 30080 HTTPS --> 30443 ... View more

Hi all, My apologies for the late reply to this thread! The WS dependency was ultimately replaced at 2023.3 with a traditional RESTful protocol. Issues related to this should resolve themselves as part of the upgrade. ... View more

Hi @Pat_Gallagher , I believe the issue you are encountering is a bug which prevents the schedule DB maintenance task from running, and new partitions are not created. This will be addressed in a 2023.3.1 patch we're compiling. As a workaround, running this manually via Admin > Database > Run should alleviate the issue and metrics data should begin to appear. If not, please reach out to support and we can diagnose further.   Hi @IrisHadarStltd @GJameson , We haven't been able to readily reproduce the "Retention management failed for table 'metrics_data'" error after an upgrade. Would you please reach out to support to get a ticket started? This will get us get more information to diagnose.   Thanks, ... View more

Hi folks, The dev team has been working with support today and have made good progress. We'll have a writeup this early week and share more information then. ... View more

Hi Pat, Would you reach out to Support to start the diagnosis process? Thanks! ... View more

Thanks Matt - we'll look into how this can be supported ... View more