|
POST
|
@HarithaVendra, Development work has just finished on the patch. It will be released in mid-October.
... View more
09-19-2024
07:36 AM
|
1
|
3
|
1614
|
|
POST
|
Hi everyone, Thank you all for your patience as we look into this. The Monitor development team has identified the cause of this issue. A fix will be included in the upcoming 2024.0.1 patch. This issue is officially recorded as BUG-000170617. Josh cc: @SteveMcCarthy @RexNeville @BrittanyBurson @ChrisTaylor2
... View more
09-13-2024
07:40 AM
|
0
|
10
|
2804
|
|
POST
|
Hi @Justin_Greco, The components deleted event, in this scenario, would only fire if the component was actually removed from the system (a.k.a. the service is deleted from ArcGIS Server). In the current release of ArcGIS Monitor, there is not a straightforward way of receiving a notification when a service enters the stopped state. I discussed this use case with the development team at length and I think there are a few features that will meet this need. In the near term, ArcGIS Monitor will have the ability to monitor HTTP endpoints. One of the metrics that Monitor will collect for HTTP endpoints is whether a connection can be made to the target URL. Failure to do so may indicate that a service is in the STOPPED state or is otherwise unusable. This feature will also allow you to specify a regex pattern that will be used against the response body to look for matches. This means you could choose to monitor the HTTP endpoint that reports the system state of a critical service and search for the string "STARTED" in the response body. If this string is not found, an alert will be opened and you will be notified. In the longer term, the development team will add the ability to open alerts based on attribute changes. System state is one example of an attribute on an ArcGIS Server service. Please let me know your thoughts on these features and if there are any other questions I can help answer. Josh
... View more
09-11-2024
11:50 AM
|
2
|
1
|
875
|
|
POST
|
@CharlotteNCIT, We are not able to reproduce this behavior in house. Two action items here: 1. Submit a case with Esri Support to investigate further. 2. Install as another account (domain or local, non-gMSA), then manually switch the service account via Windows Services if the installation is successful. = Thanks, Josh
... View more
09-10-2024
07:45 AM
|
1
|
1
|
1095
|
|
POST
|
@Raleigh_GISGIS, what version of Portal are you using?
... View more
09-04-2024
11:20 AM
|
0
|
1
|
3158
|
|
POST
|
@MichaelBartlett, Monitoring hosted services was a feature added at Monitor 2023.3. Your ArcGIS Enterprise environment must be at version 11.1 or above to take advantage of this feature. Josh
... View more
09-04-2024
07:23 AM
|
1
|
0
|
792
|
|
POST
|
In order to be helpful, I will need more context about what you mean by "would not install". Is the installer failing? Are you seeing an error message?
... View more
09-03-2024
10:34 AM
|
0
|
3
|
1187
|
|
POST
|
@CharlotteNCIT, it did not. GMSAs are still supported.
... View more
09-03-2024
09:08 AM
|
1
|
5
|
1202
|
|
POST
|
Hi everyone. The development team has identified the issue and provided the solution to Esri Support. I also want to provide the solution here for those who are comfortable running SQL commands against PostgreSQL databases. If you do not have experience administering PostgreSQL, please reach out to Esri Support for help performing this workflow. The cause of this issue is a small bug in the upgrade process that leaves all child components (service, storage, and connector) in the migrated state after an agent is configured on the host machine, whereas the state of these components should be changed to monitored at that point in time. The solution is to 1) identify all of the effected components and 2) update their state from migrated to monitored. Here are the steps to do so: Stop the ArcGIS Monitor Server service. Connect to the ArcGIS Monitor database in pgAdmin. Open a new query window. Issue the query below, which will list all of the child components whose state is migrated but whose parent component state is monitored SELECT * FROM "components" AS "C1"
WHERE
STATE = 'migrated'
AND EXISTS (
SELECT
*
FROM
"components" AS "C2"
INNER JOIN "component_connections" ON "C2"."id" = "component_connections"."parent_id"
WHERE
((STATE = 'monitored'))
AND ("C1"."id" = "component_connections"."child_id")
) 5. If there are one or more results from the query above, issue the query below, which will align the child component states with their parent component (migrated to monitored). UPDATE "components" AS "C1" SET STATE = 'monitored'
WHERE
STATE = 'migrated'
AND EXISTS (
SELECT
*
FROM
"components" AS "C2"
INNER JOIN "component_connections" ON "C2"."id" = "component_connections"."parent_id"
WHERE
((STATE = 'monitored'))
AND ("C1"."id" = "component_connections"."child_id")
) 6. Issue the query from step 4 again. If step 5 was successful, no records should be returned by this query. 7. Start the ArcGIS Monitor Server service and verify that the service components are now visible via the ArcGIS Monitor web UI. Alternatively, a patch that addresses this issue will be available in the coming weeks. Josh
... View more
09-03-2024
08:58 AM
|
5
|
2
|
3873
|
|
POST
|
Hi everyone. The development team has identified the issue and provided the solution to Esri Support. I also want to provide the solution here for those who are comfortable running SQL commands against PostgreSQL databases. If you do not have experience administering PostgreSQL, please reach out to Esri Support for help performing this workflow. The cause of this issue is the presence of empty Analysis Views or Analysis Views that only contain Header elements. The solution to this issue is to remove all empty Analysis Views and restart the ArcGIS Monitor Server process. If you have already rolled back to a previous release, you can simply delete any empty Analysis Views through the web GUI and then re-run the upgrade. If your ArcGIS Monitor installation is stuck in the state described in this post, you can manually delete the Analysis Views from the database. To do so: Stop the ArcGIS Monitor Server service. Connect to the ArcGIS Monitor database in pgAdmin. Open a new query window. Issue this query: SELECT * FROM ANALYSES Take a CSV backup of the results. 6. Delete any row where the expressions array under the configuration column is empty or is missing entirely. For example, a row with the configuration object below would be deleted, because the expressions array is [] (empty): 7. Start the ArcGIS Monitor Server service and try accessing the application again. If the problem persists, please reach out to Esri Support for further troubleshooting. Alternatively, a patch that addresses this issue will be available in the coming weeks. Josh
... View more
09-03-2024
08:44 AM
|
8
|
1
|
5503
|
|
BLOG
|
@Hannah24, the system requirements for Monitor 2024.0 can be found here.
... View more
09-03-2024
07:46 AM
|
1
|
0
|
3823
|
|
POST
|
Hi @ChrisTaylor2 , Sorry to hear your services aren't showing up post-upgrade. We think we have a good understanding of what is happening. Can you submit a case with Esri Support so they can triage this a bit further and provide additional information to the dev team? By the way, please do not unregister the ArcGIS Server sites. We should be able to recover the services and still leave your configuration in tact. Josh
... View more
08-28-2024
12:12 PM
|
1
|
3
|
4126
|
|
BLOG
|
Introduction ArcGIS Monitor 2024.0 was released on August 27th, 2024. One major change in this version is that the ArcGIS Monitor Agent software is required on all machines in the ArcGIS Enterprise environment that you wish to collect metrics on. This is different from previous releases, where metrics could be collected on all components using a single agent. To make the deployment of agents across the environment quicker, my colleague @GeoJen and I have written a set of scripts to automate the process. The first script, InstallAgents, takes a list of machines, connects to the targets remotely, and installs the ArcGIS Monitor Agent 2024.0 software. The second, ConfigureAgents, takes a list of machines, connects remotely, completes the Agent post-installation steps, and completes registration with your ArcGIS Monitor Server. The scripts can be downloaded here. Requirements To use these scripts, you must: Be running Windows Have ArcGIS Monitor Server 2024.0 installed and configured. Have the ArcGIS Monitor Agent 2024.0 installer downloaded on a central location. Be running Powershell 5.1 or above Be an administrator on the machine where the script is run and on the machines targeted for Agent configuration. Have credentials for an ArcGIS Monitor Server user with the Administrator role. Usage InstallAgents 1. Open a Powershell 5.1 prompt and change directories to the folder where you downloaded the scripts to. 2. Launch the script: .\InstallAgents.ps1 3. Provide a commas-separated list of machines where Agents should be installed: Target Machines (comma-separated list): machine1.esri.com,machine2.esri.com,machine3.esri.com 4. Enter the credentials for the account that will be used to run the ArcGIS Monitor Agent service: Connection Credentials
Enter credentials for a user who is an administrator on all target machines
User: myDomain\josh
Password for user myDomain\josh: **************** 5. Provide the path to the ArcGIS Monitor Agent installer directory. This should be the folder that contains Setup.exe: ArcGIS Monitor Agent Installer: C:\Users\<username>\Documents\ArcGIS Monitor 2024.0\MonitorAgent After completing these steps, the script will create a remote Powershell connection to each machine specified and install the software. The output will look like this for successful installations: *********************
machine1.esri.com
*********************
Creating remote session...
Copying installer to remote destination...
Installing ArcGIS Monitor Agent 2024.0...
Installation successful!
*********************
machine2.esri.com
*********************
Creating remote session...
Copying installer to remote destination...
Installing ArcGIS Monitor Agent 2024.0...
Installation successful! ConfigureAgents 1. Open a Powershell 5.1 prompt and change directories to the folder where you downloaded the scripts to. 2. Launch the script: .\ConfigureAgents.ps1 3. Provide a commas-separated list of machines where Agents are installed and need to be configured with ArcGIS Monitor Server: Target Machines (comma-separated list): machine1.esri.com,machine2.esri.com,machine3.esri.com 4. Enter the ArcGIS Monitor Server URL that the targeted Agents should be configured with: ArcGIS Monitor Server URL: https://monitorserver.esri.com:30443/arcgis 5. Enter the username and password of an ArcGIS Monitor Server user that has the Administrator role: ArcGIS Monitor Server Credentials
Enter credentials for an administrator user in ArcGIS Monitor Server
User: adminuser
Password for user adminuser: ************************* After completing these steps, the script will create a remote Powershell connection to each machine specified and configure the ArcGIS Monitor Agent software with ArcGIS Monitor Server. The output will look like this for successful configurations: *********************
machine1.esri.com
*********************
Creating remote session...
Checking for ArcGIS Monitor Agent installation...
Trying to reach ArcGIS Monitor Agent via HTTP...
ArcGIS Monitor Agent reachable!
Configuring with ArcGIS Monitor Server...
[ success ] Successfully authenticated to ArcGIS Monitor Server
[ success ] Successfully registered to ArcGIS Monitor Server
*********************
machine2.esri.com
*********************
Creating remote session...
Checking for ArcGIS Monitor Agent installation...
Trying to reach ArcGIS Monitor Agent via HTTP...
ArcGIS Monitor Agent reachable!
Configuring with ArcGIS Monitor Server...
[ success ] Successfully authenticated to ArcGIS Monitor Server
[ success ] Successfully registered to ArcGIS Monitor Server
... View more
08-28-2024
11:28 AM
|
9
|
17
|
5252
|
|
POST
|
Hi @WhitneyLoy and @EdenPunter, Are you also upgrading from 2023.1 --> 2024.0 or are you upgrading from another version? Dev team is investigating. Thanks, Josh
... View more
08-28-2024
06:03 AM
|
0
|
3
|
3279
|
|
POST
|
Hi @MichaelBartlett, Services are automatically added and removed from ArcGIS Monitor by the ArcGIS Server Discover observer. Go to the ArcGIS Server component > Settings > Observers > Discover and try running it manually by clicking "Run Observer". Josh
... View more
08-20-2024
06:53 AM
|
1
|
1
|
888
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-01-2025 05:40 AM | |
| 1 | 02-28-2025 07:11 AM | |
| 1 | 01-16-2025 05:35 AM | |
| 2 | 01-14-2025 06:48 AM | |
| 2 | 01-10-2025 08:07 AM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|