nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Host CPU Utilization graph shows high CPU but the performance graph on the server shows little activity

Royce_Simpson

Having an odd issue that just started in the last day or so, where I'm getting high CPU usage alerts from the ArcGIS Monitor server machine (registered host component), but when I log into that server and look at the CPU performance graph native to the OS, I see very little activity, everything well below the alerting thresholds.

Is there a reason Monitor would report different readings than what the server is directly showing?

Find more posts tagged with

Accepted answers

All comments

DerekLaw

Hi @Royce_Simpson,

ArcGIS Monitor should report the same CPU host metrics as the CPU performance graph of the host. Can you please share some more details and maybe screenshots of what you're seeing? Which release of ArcGIS Monitor are you using?

To confirm, this would be for the same time period/range right? Is this for a Windows or Linux host? Are you only seeing this behavior for a single host, or for all your host machines?

Royce_Simpson

Here are a couple screenshots of the task manager cpu stats on the server vs ArcGIS Monitor. The time scales are different but task manager on the server is consistently below 20% on average, whereas ArcGIS Monitor is showing consistantly above 60%.

ArcGIS Monitor 2025 (2025.0.0+856). Windows Host.

Monitor

Server Task Manager

DerekLaw

Hi @Royce_Simpson,

Apologies for the late reply.

Are you seeing this behavior for just 1x - GIS Server host, or for all of your registered GIS Server hosts? If the former, anything that makes this particular host different from the others? Does it have other software running?

Royce_Simpson

Just the one. The only thing that makes it different, as far as I can tell, is that it's the server with ArcGIS Monitor installed. No other software is installed.

You can see from the screenshot that the ArcGIS Monitor CPU is always high compared to all the other servers. Task Manager on that server reports an average of 10-15%.

anasga_81182

Hi @Royce_Simpson ,
I have had the same problem as well after upgrading to 2025.0.1. It was one of my servers which Monitor showed that it has a high load-cpu which was not the truth when checking inside the machine.

I have now reverted back to 2024.1.1 as in this case i can not trust that any other machines would have later the same problem as well as i do see a lot of problems with the 2025.0.1 and hopefully some patches will come soon
//Anas

DerekLaw

Hi @anasga_81182,

> I have had the same problem as well after upgrading to 2025.0.1. It was one of my servers which Monitor showed that it has a high load-cpu which was not the truth when checking inside the machine.

Can you please open an Esri Tech Support case so they can collect information/background on your deployment? We're looking for as much info as possible and steps to reproduce this behavior.

Getting valid repro steps is the only way we can investigate and resolve.

MarcoMedeirosPTBR

Is there any updates about this behavior?

Nryan

Hello! I just had the pleasure of debugging this oddity in our server. 😂
This happens because of the scheduled observers. The observer that grabs the system metrics is "Metrics - Host Windows". This (for us) is scheduled to occur every 1 minute. Other observers were also scheduled to occur every 1 minute.

In other words, the CPU Utilization is the exact CPU Usage % of when the "Metrics - Host Windows" observer runs. Since other observers run at this exact same time, it causes a brief CPU spike.

If you measure the CPU Spike from Performance Monitor, it exactly matches what Monitor Displays.

Setting "Metrics - Host Windows" to check every 1 minute, and others at other times, creates a much more accurate chart. An example is below.

In below example, system metrics are recorded every 1 minute while all other observers run every 5 minutes. You can see the dramatic spike that happens every 5 minutes.

To be honest, it's a pretty serious configuration flaw with observer scheduling. 😂 ESRI should include an option to where we can stagger the observer run times. Example, start running at "00:00:30" with a repeat interval of 1 minute. This would perfectly fix this problem!

Please vote for this idea here!!! https://community.esri.com/t5/arcgis-monitor-ideas/add-start-time-setting-for-observers/idi-p/1712875

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.