Latest Contributions by EsriEvan

‎04-10-2025

@EricJohnson-HDR - Thanks for sharing the latest. Acknowledging the OS updates, I am a bit troubled the Agents did not heal their own connection after some time 🤔. Will definitely flag this for future dev investigation.

‎04-10-2025

Hi @SteveMcCarthy @EricJohnson-HDR, @GrahamWood-HWC Thanks for sharing - I have been studying this and wanted to ask if you both wouldn't mind sharing a couple things: 1. Execute the following query in your Monitor Postgres and sharing the result. This will help me rule some things out. SELECT (SELECT last_value FROM metrics_id_seq) as metrics_id_seq, (SELECT last_value FROM components_id_seq) as components_id_seq, (SELECT last_value FROM observers_id_seq) as observers_id_seq; 2. Would you also confirm that the Agents in question show connected or disconnected? If they are disconnected, confirm we have attempted to re-register the Agent to Server using the --agent-id XYZ parameter? Also wanted to share some thoughts related to other comments above: - "Token expired logs seen" - these are probably just from the front end's natural token expiration / refresh and are beguine. Agent tokens do not expire. - "Losing Components etc" - as long as the Agent is not "unregistered" the related Components and data would not be lost. If an Agent does somehow lost connection (as we are investigating here) one thing to try is go to the Agent and use the CLI "disconnect" and "register" using the --agent-id parameter to reregister the existing Agent and attempt to re-establish

‎02-12-2025

Hi, Most likely the second site is being identified as a "duplicate". At 2024.1, this is done by evaluating an identifier added to the ArcGIS Server properties config. Please check both servers and see if they somehow match. If they do, the property can be removed from one of the Servers and re-registered with Monitor. See below reference in the documentation: https://doc.arcgis.com/en/monitor/latest/get-started/windows/register-arcgis-server.htm#:~:text=The%20monitorSystemId%20field%20is%20added%20to%20the%20Server%20Properties%20object%20and%20contains%20a%20unique%20identifier%20for%20the%20ArcGIS%20Server%20site.

‎02-05-2025

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.

‎01-30-2025

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!

‎01-08-2025

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

‎09-06-2024

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.

‎06-28-2024

Hi @SGTomlins That particular metric is instrumented within ArcGIS Server itself, which ArcGIS Monitor directly acquires via ArcGIS Server usage reports. Monitor does not perform any additional aggregation at the service level.

‎04-03-2024

Hi folks, The dev team took a look at this and there is a bug related to the hashed value added to the X-esriHook-Signature header. For future reference, it should be a sha256 as Kevin described above. Definitely a bug. We'll address this in the next release and include documentation how to match on the receiver side (similar to what Kevin originally went with) Very sorry for the confusion here, and thanks,

‎02-23-2024

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

‎12-22-2023

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.

‎12-21-2023

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

‎12-21-2023

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.

‎12-21-2023

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,

‎12-18-2023

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.

Online Status	Offline
Date Last Visited	‎04-23-2025 07:27 AM

My Ideas

Latest Contributions by EsriEvan

Re: Monitor 2024.0.1 - All monitored hosts are disconnected

Re: Monitor 2024.0.1 - All monitored hosts are disconnected

Re: ArcGIS Monitor 2024.1 - Issue registering ArcGIS Server Single-machine high-availability (active-active) deployment.

Re: ArcGIS Monitor 2024.1 Instance Saturation Percentage for ArcGIS Services all at zero

Re: 2024.1 ArcGIS Datastore Invalid Version: 11.3.0.51575

Re: Register SQL serever as SAAS

Re: ArcGIS Monitor 2024.0 Unable to Generate Token when Registering Portal

Re: What is measured for the "Average Response Time" ?

Re: Validating WebHook Secret

Re: ArcGIS Monitor not starting after upgrading to 2023.3.1

Re: Monitor 2023 Adonis Warning

Re: Connecting to ArcGIS Monitor 2023 through IIS

Re: Connecting to ArcGIS Monitor 2023 through IIS

Re: Monitor 2023.3 database connection

Re: Monitor 2023.3 database connection

Re: Monitor 2024.0.1 - All monitored hosts are dis...

Re: Monitor 2024.0.1 - All monitored hosts are dis...

Re: ArcGIS Monitor 2024.1 - Issue registering ArcG...

Re: ArcGIS Monitor 2024.1 Instance Saturation Perc...

Re: 2024.1 ArcGIS Datastore Invalid Version: 11.3....