I just added a host component to ArcGIS Monitor and the sqlserver.exe metrics are incorrect. It's showing 0.0 CPU utilized, memory used, and memory utilization:
Task Manager on that server shows sqlserver.exe CPU ranging from 0.5% - 20% for the last hour and memory used at around 9K MB.
Am I missing something?
Hi @N8-CORR,
Can you please provide more information,
-
Hi @DerekLaw,
See answers below:
You can see here that it records Memory Utilized no problem, but not CPU:
If only memory metrics are showing, please see this AGM forum post.
If your service account is already a member of the Performance Monitor Users groups then I would suggest to first try restarting the Agent Service on the VM Host’s that have this issue.
Hi @StevenBeothy, thanks for the helpful reply. I can confirm that I have added the service account to the Performance Monitor Users and Remote Management Users groups:
I also made sure I added the account which I used to register the component to those same groups:
For extra measure, I also enabled permissions for WMI cimv2 (even though I'm at 2025.01):
Needless to say, I have restarted the ArcGIS Monitor Agent and Windows Remote Management services multiple times but I still can't get CPU metrics to appear:
Hi @N8-CORR
Please note that ArcGIS Monitor has never supported Windows Server 2012 R2 and the last release of ArcGIS Enterprise that supported this OS was 10.9.1 which goes into mature status next week on Dec.1, 2025. This OS also had standard support ended by Microsoft on Oct. 10, 2023.
This unsupported OS version may or may not be related to your issue but it would be recommended to upgrade as even Esri Support will not be able to help if minimum system requirements are not met.
Not that this should be the cause of your issue, but please note your ArcGIS Monitor Agent shown in the screenshot was installed with a local account and not the above stated domain account. Best practice would be to have all components installed with either a domain services account or gMSA but local accounts can also work. When going through the installers be sure to include your domain (DOMAIN\username).