The Resources check reports the CPU and memory status of each domain controller (DC) or read-only domain controller (RODC). The ENow client collects the data with a WMI query against the server's performance counters, and the status shown is the collected value compared against the threshold set for the check in the console.
Where the thresholds are set
CPU and memory thresholds are configured in the ENow Admin Console, under Server > Tuning Policy > Agent Options. The check does not use a fixed value, so confirm the current warning and critical levels in your own console.
Verify the result ENow recorded
From EMS 8.0 onward, collected results are held in the ENow SQL database rather than in files on the web server. Open the Resources monitoring page for the domain controller in the ENow console to see the CPU and memory values ENow last recorded, and the status it assigned them.
Verify the result on the ENow client
The client stores its collected results on the monitored domain controller itself:
\Program Files (x86)\ENow\Mailscape Agent\Cache\ResourceAgentMessage.xml
Not everything the client collects is written to the log, so this file is the authoritative view of what the agent last saw. It is on the monitored server, not the ENow web server.
Confirm CPU usage by hand
Run this on the DC or RODC being monitored:
Get-WmiObject Win32_Processor | Select LoadPercentage
Confirm memory and page file usage by hand
Run these on the DC or RODC being monitored:
Get-WmiObject -Class Win32_PageFileUsage | Select AllocatedBaseSize, Description, InstallDate, Name, PeakUsage, TempPageFile | Format-List
Get-Counter "\Memory\% Committed Bytes In Use"
If the values you see by hand are within your configured thresholds but ENow still reports a warning or error, the difference is usually the monitoring service account's rights to query WMI on that server rather than the resource level itself.
Comments
0 comments
Article is closed for comments.