Hi, We have a client where Pulse was reporting Server RAM usage at 90%, but the Server was actually showing 40%. I’m wondering what metric Pulse is reporting eg. Working Set, Peak Working Set, Commit Size, Paged Pool etc.
Thanks
Mal
Hi @mmacdonnell,
Pulse is using a library that retrieves these information via a Windows API call. There is not much details we can provide here as those stats are coming from the API itself for which we do not have much control or visibility from. As noted, there is a lot of aspect with memory stats. And what one might see in the Task Manager is a snapshot at a point in time and may differ and is often not exactly but should be close given another memory viewer.
Even with CPU, if you compare the details via Task Manager at process and at server level, does not give you an exact calculation or close estimate at times.
Perhaps a different perspective to this is - does it stays at that usage rate? Or does it fluctuate a lot? That might help give a clue as to what the server is doing in general and might help explain the fluctuating metrics - or the difference in metrics at times in general.
Cheers,
Paul
Sometimes Pulse does get “stuck” especially if the remote server has experienced a CPU spike effectively disconnecting the monitor agent. Going to the environment administration and resaving the connection can restore the monitoring KPIs, or else restarting the pulse-server service itself.