Individual service metrics are missing in my 2024.1 installation monitoring a 10.9.1 Enterprise.
Just a guess for my 10.9.1 install, but the usage report shows resources with 2 seeming issues. First is this ":<serviceType>" after the name and before the ".<serviceType>". Second is the service names are all lowercase. I copied the agm usage report json, created my own, and could verify that every service returns NODATA. Changing either the service folder and name to the correct case or removing the ":gpserver" did not result in valid data returned, but fixing both does. So this should look like "services/System/CachingControllers.GPServer" not "services/system/cachingcontrollers:gpserver.GPServer'.
Here's a comparison of the usage reports from 10.9.1. 2024.1 on the left vs 2024.0.1 on the right.
I don't recognize your screen grabs. Where are are you generating these usage reports from?
These are accessible from the admin endpoint. https://developers.arcgis.com/rest/enterprise-administration/server/usagereport/
I am on AGM 2024.1 now as well and my service metrics are also missing. I am monitoring ArcGIS Enterprise 11.4. I checked ArcGIS Server and the metrics are there in its Statistic Reports page. However, I thought there used to be an ArcGIS Monitor report on the Statistics Reports page that I am no longer seeing. Did something change at 2024.1?
ok @DavidJantz I am seeing the same thing. I dk. I'd say lets see what the 2024.1 patch does once that comes out.
All,
Apologies for this issue. The Monitor team is working on a patch to resolve this. I will post an update when we have news to share. Thanks for your patience.
Hope this helps,
Could someone please share the ESRI incident ticket number with us? We're encountering the same issue and would like to attach ourselves to the ticket as well.
Hannah
Hi @HannahHe1,
Please contact Esri Tech Support and open a Tech Support incident. They will add your reported issue to the internal BUG tracking system.
Hope this helps,
I logged a ticket with ESRI, and it has been tagged with the following issue. Could you kindly confirm if this is the correct issue to be tagged? Also, could you please provide any estimated timeframe for fixing this issue? In case it might take a while, would you recommend reverting to the previous version 2024.0? Hannah