Select to view content in your preferred language

Monitor 2024.1 missing Service Request data (number of requests, response times, etc)

1479
14
Jump to solution
03-12-2025 07:18 AM
ChaseBarnard
Occasional Contributor

I've recently installed Monitor 2024.1 on a new server.  I had previously been running 2023.* on a different machine. I've successfully registered 4 agents on 4 separate machines in our Enterprise.  Monitor Server is recognizing all the components including 323 service components.  Likewise, all the infrastructure telemetry seems to be coming in correctly.  What I am not seeing is any data on the ArcGIS-side including data on requests received, request response time, ArcSOC instances used, etc.  Logs indicate various codes including "E_AUTH_TOKEN_EXPIRED" and "E_AUTH_INVALID" but I haven't been able to track down the issue.  Any suggestions?

Tags (2)
14 Replies
DerekLaw
Esri Esteemed Contributor

Hi @NicolasNi1977,

Apologies for the late reply. I was working at the ERGIS 2025 conference last week in Houston, TX.

For the error message in the first screenshot, can you please login to the ArcGIS Administrator Directory for the ArcGIS Server site >  then navigate to SiteRoot > usagereports

Are there any reports that start with a numerical character? If so, can you please delete them. Then restart the AM Agent service on the machine.

Hope this helps,

 

0 Kudos
LachlanWainwright
Occasional Contributor

Hi @ChaseBarnard 

I have a similar problem with one of my AGS sites and 2024x

I have 2 1091 ags sites connected to monitor, one is working as expected and suffering the problem above where we don't get values but the graphs show the grid etc & to be fixed soonly with the patch.

 

The other site does not capture any data at all and the monitor Server page looks like this, NO DATA:

LachlanWainwright_0-1742340559396.png

I have the same errors in the log as per yous above as well as an EPROTO.

If I manually change the from/to times in the report and manually run the observer things work and the graph changes and had data.  But it won't run on it's own again.  The report stays as LAST_DAY and won't change between LAST_DAY, 1min (when the report runs) and then going back to CUSTOM from/to with future computer time and 5mins like the other ags machines.

I have an ticket with ESRI Australia and we had this break through yesterday based on your post. Thanks a bunch mate!

This is my original post from a few weeks ago https://community.esri.com/t5/arcgis-monitor-questions/metrics-for-arcgis-server-not-displaying/m-p/...

 

@DerekLaw will the patch fix this problem as I believe it's different to the values not getting captured?

thanks 🙂

 

0 Kudos
LachlanWainwright
Occasional Contributor

Further info @ChaseBarnard 


I have had a break though with my environment.

The very short story on what I did excluding the pain of getting there.

The statistics folder for AGS was 3.2GB on the shared config location. I stopped Monitor, the  AGS, deleted all but this months dat-u/i files, fired up AGS.  Restarted Monitor & the agent on AGS. Then I had to go into the report on AGS as it still said LAST_DAY, i edited that and used https://www.epochconverter.com/ to get the right from/to times.   I set these to a time for the next run sequence as it was 14 55 for me, so 14 59 42 and 15 05 12. Edits CUSTOM, the epoch times and 5.

Then it worked finally capturing data, I'm now looking forward to the patch to fix the values

Looks like AGS or Monitor looks at all the stats files and basically times out.  Jonny T from ESRI AU tipped me into finding this by changing the agent & monitor timeouts...this led from one thing to another, yadd yadda.

 

If someone is relating to to all this and had posted the solution already and thinking I'm taking their glory shout out.  I've read some much in the last few days and don't want to steal anyone else's thunder.

0 Kudos
DerekLaw
Esri Esteemed Contributor

Hi @LachlanWainwright,

Apologies for the late reply. I was out on vacation the last 2 weeks.

> ... I'm now looking forward to the patch to fix the values

Did the ArcGIS Monitor 2024.1.1 patch resolve your issues?

0 Kudos
ChaseBarnard
Occasional Contributor
Yes, in fact, it did. Thanks for checking in.
Chase