Latest Contributions by GeoJosh

Hi @katelynjenk, This is strange, I have not seen this behavior with the 2025.0.1 release. I think the best course of action is to log a case with Support to troubleshoot further. The fact that this is occurring on one machine but not others points to an environmental / configuration issue on the machine itself, which Support should be equipped to help narrow down. Josh ... View more

Hi @RahulRaj2025, Can you please post a screenshot of the error you are getting when registering the components? Josh ... View more

Hi @KTuri, ArcGIS Monitor Agent needs to be installed on a machine where it can communicate with both the database cluster through the port you mentioned and ArcGIS Monitor Server through port 30443. You will need to update your firewall rules to allow traffic through the default port between the database machine and where the ArcGIS Monitor Agent is installed, since this is the piece of software that will actually be interfacing with the database to collect metrics. Let me know if I can clarify further. Josh ... View more

Hi @Oiligriv, Unfortunately I lack the context to know why the service stopped in the first place. A few suggestions: ArcGIS Monitor Agent logs are located on the agent machine at this location by default: C:\Users\<username>\AppData\Local\ESRI\ArcGISMonitor\config-store-agent\logs\agm-logs.sqlite. You can use DB Browser for SQLite to open the logs database and see if any more detailed information was logged. If this happens regularly, it might suggest a problem related to communication between agent and server. I recommend working with Esri Support in this case. You can configure an alert in ArcGIS Monitor Server to let you know when an agent becomes disconnected. While not a solution to the problem, it would minimize the time that data is not being collected:   Josh ... View more

Table element will be added at ArcGIS Monitor 2024.1. ... View more

Hi @VirgilioPalmi, when you are re-registering the agent, are you including the --agent-id flag? If the agent is already present in ArcGIS Monitor Server, then you need to include this flag, followed by the ID of the agent in question. You can find the agent ID by going to ArcGIS Monitor Server > Monitoring > Agents, and enabling the ID column: To re-register the agent, the command should look like this: ./arcgis-monitor-agent.exe admin:system:register --server-url https://agmserver:30443/arcgis --username admin --password MyPassword!1 --agent-id 2 Josh ... View more

Hi @AntheaTung, At current release, there isn't a way to get alerted when an ArcGIS Server service enters the STOPPED state due to the way this property is tracked (it is tracked as an attribute, rather than a metric). In the future, we plan on allowing alerts to be set up on attributes which would meet this use case. In the meantime, can you please upvote this idea to show your support? https://community.esri.com/t5/arcgis-monitor-ideas/alert-on-the-status-of-a-service-stopping-starting/idi-p/1265854 Josh ... View more

Hi @ThomasM, That's a really strange and specific error message to get on agent registration. Can we check to make sure the upgrade was actually successful on the AGM Server side? If you log into AGM Server and click your username in the upper-right, what version do you see reported? Josh ... View more

@i3Admin, If you have a collection whose expression references an agent ID field, the collection must be removed before upgrading and recreated post-upgrade. Josh ... View more

Hi@CaseyBurns, The script is missing a -credential switch in the code. The following line needs to be corrected: -Credential was deliberately left off because we assume that the user running the script has admin access to the target machine (see bullet point 5 in the original post under "Requirements"). If this is true, then the script block should run as the current user on the remote machine. The ConfigureAgents script is attempting to use an active directory username/password instead of an internal username/password for ArcGIS Monitor. The line below, needs to be changed to reflect internal ArcGIS Monitor user. GetNetworkCredential().Username is simply pulling the Username value from the credential object created at the beginning of the script, which do not necessarily have to be domain/network credentials. As long as you provided the username and password for an ArcGIS Monitor Server user with the admin role for that prompt, they should be parsed correctly. Please try reverting to the original script, run it as a user who is an admin on the local machine and the target remote machines where you wish to configure monitor, and ensure you provide an ArcGIS Monitor Server username and password for the prompt ArcGIS Monitor Server Credentials. If you're still seeing this failure, send me a DM for further troubleshooting. Josh ... View more

@AnasKanaan, The license is the same for 24.0 and 24.0.1, so I don't think that is the issue. Follow the steps below: 1. Stop the AGM Server OS service. 2. Open a Powershell prompt on the AGM Server machine as the OS account running the AGM Server service. 3. Change directories to the AGM Server installation directory (C:\Program Files\ArcGIS\Monitor\Server\bin by default). 4. Run the AGM Server binary with debug logging enabled: > $env:LOG_LEVEL='debug' > ./arcgis-monitor-server.exe --serve 5. Let the software boot for about 30 seconds. 6. Copy the output from the terminal and provide it in a direct message to me. Thanks, Josh ... View more

Hi @SteveMcCarthy, There is no harm in installing agents on the server machines, shutting the OS service off, and turning them back on and completing registration with AGM Server once it has been upgraded to 24.0.1. Josh ... View more

Hi Pat, I'm not able to reproduce an upgrade error from 23.3.1 --> 24.0.1 on my side. These types of issues are usually specific to the ArcGIS Monitor instance so I don't think it will be efficient to troubleshoot this over the forum. Can you please submit a case with technical support to take a more detailed look? Thanks, Josh ... View more

@AYUSHYADAV, Have you upgraded both ArcGIS Monitor Server and Agent? This may require a deeper look into your environment. Please submit a new case with Esri Technical Support. Josh ... View more