jbiggley ✭✭✭✭✭

I got it to work today -- totally different method. None of the fun error trapping that xander.snyder had in his but it works! (Which, after the week I've had banging my head against the wall on this one, is a minor triumph.) $process = Get-WmiObject win32_process -ComputerName '${IP}' -Credential '${CREDENTIAL}' |…

To close off this thread, we had opened incident 737340 with support. What we determined was that in our environment (NPM 11.0 and SAM 6.1.1 installed) when you were polling CPU and memory utilization via WMI and then remove those resources from monitoring the Nodes table does not get updated with the current value. The…

This is a mashup of two alerts that we already use as a possible answer to question 3 above. I chose 6 minutes because our data collection interval is 5 minutes. I mashed the italicized/bolded parts into The Ultimate CPU Alert to allow us to check to ensure that the data in the CPULoad_Detail table was current. I've tested…

Still waiting for an answer from the development team on this one. Stay tuned!

For the record, I did find a statistic over at the VMware vSphere API Reference. Search All Properties for ScsiLUN, specifically the queuedepth property.