2024.1 Individual Service Metrics Missing

[DavidJantz]

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'.

[HannahHe1]

I'm considering reverting back to version 2024.0 due to some issues we've encountered with version 2024.1. Could you please let me know if there have been any schema or data structure changes in the PostgreSQL database with this latest release? Additionally, would it be necessary to restore the PostgreSQL database if we decide to revert?  Hannah

[DerekLaw]

Hi @HannahHe1,

> Could you kindly confirm if this is the correct issue to be tagged?

Yes, that's the issue.

> Also, could you please provide any estimated timeframe for fixing this issue?

The team is working to address several bugs for the Monitor 2024.1.1 patch. We're expecting to have it ready for early March timeframe. 

> In case it might take a while, would you recommend reverting to the previous version 2024.0? 

It's really up to you. 

> Could you please let me know if there have been any schema or data structure changes in the PostgreSQL database with this latest release?

Yes, there were some internal schema changes in the AM database.between releases. 

> .... would it be necessary to restore the PostgreSQL database if we decide to revert? 

Yes. In the upgrade help documentation, we state that you should create a backup of your AM database before upgrading to the new release. 

Hope this helps,

[DerekLaw]

All,

UPDATE: the ArcGIS Monitor 2024.1.1 patch that addresses this issue is scheduled for release on March 20. 

Thanks for your continued patience,

[marceloctorres]

ArcGIS Monitor 2024.1.1 released on MyEsri

[IDOTAdmin]

I applied the ArcGIS Monitor 2024.1.1 patch, and everything appeared to be functioning normally. However, today I noticed a gap in the analysis view. All agents are connected, and there are no critical alerts. What could be causing this?

[DerekLaw]

HI @IDOTAdmin,

> ... today I noticed a gap in the analysis view.

By "gaps" do you mean the "empty" timeslots, such as at 12:30 and at 1:25? So your expectation is to see some data points at these timeslots, right? This behavior is really odd.

Some things to try to troubleshoot:

• Can you please restart your AM Agent service on the host machine;
• Can you please manually run the ArcGIS Server component's Metrics observer;
  (navigate to Monitoring page > select the ArcGIS Server component > Observers > select the Metrics observer > View observer details > Run Observer)
  
  
• When change the serial chart display option to line type, do the data points appear?

Hope this helps,

[IDOTAdmin]

Hi, Derek

Thank you for your prompt response. I followed your suggestion this morning at 6 AM EST and am hopeful that the bar chart will return to normal today.

I did followings: 

•  restart your AM Agent service on the host machine;
•  manually run the ArcGIS Server component's Metrics observer;
  (navigate to Monitoring page > select the ArcGIS Server component > Observers > select the Metrics observer > View observer details > Run Observer) 
  
  Many Thanks

[IDOTAdmin]

I did what recommended and also restart ArcGIS Monitor Server,  still see the timeslot gap.

[DerekLaw]

Hi @IDOTAdmin,

> ... still see the timeslot gap

I'm sorry you're still seeing this behavior. I've only heard of this happening once before, but we were unable to reproduce this behavior. Can you please contact Esri Tech Support so they can take a closer look and try to reproduce this issue? 

[IDOTAdmin]

I identified the root cause of the issue: the blank time slot corresponds with the ArcGIS Monitor log, where the Observer failed to read the ArcGIS Server usage report.