Dear Marcel

This is a weakness of WMI which we cannot solve from our side. For for information please have a look at this article https://kb.paessler.com/en/topic/1073 chapter "Nonsensical or wrong results".

I am using a Powershell custom EXEXML sensors to monitor the RAM on a 64-bit process.

Just put this code into your "Custom Sensors\EXEXML" folder and create a new EXEXML sensor. I also set the Security Context to "Use Windows credentials of parent device".

Just modify the "HOST" value with the hostname of your server and modify the "PROCESS" value with the name (without .exe) of the process you wish to monitor.

For example to monitor the WinLogon.exe process only input "winlogon". $ProcessName = Invoke-Command -ComputerName Server01 -ScriptBlock {Get-Process -Name "winlogon" }

# Get Process Info
$ProcessName = Invoke-Command -ComputerName HOST -ScriptBlock {Get-Process -Name "PROCESS" }

# Output PRTG XML Data
write-host "<prtg>"
write-host "<result>"
write-host "<channel>"
write-host $ProcessName.ProcessName
write-host "</channel>"
write-host "<unit>BytesMemory</unit>"
write-host "<value>"
write-host $ProcessName.WorkingSet64
write-host "</value>"
write-host "</result>"
write-host "</prtg>"

Edit by Paessler Technical Support

The following script (adapted from above) allows you to pass the host and process as a parameter, rather than hardcoding it in the script itself.

param(
[string] $machine,
[string] $processName
)
# Get Process Info
$myargs = @{ ProcessName = $processName }
$processInfo = Invoke-Command -ComputerName $machine -ScriptBlock { 
	PARAM($myargs);
	Get-Process -Name $myargs.ProcessName 
} -argumentList $myargs

# Output PRTG XML Data
write-host "<prtg>"
write-host "<result>"
write-host "<channel>"
write-host $processInfo.ProcessName
write-host "</channel>"
write-host "<unit>BytesMemory</unit>"
write-host "<value>"
write-host $processInfo.WorkingSet64
write-host "</value>"
write-host "</result>"
write-host "</prtg>"

Now when you add the script within PRTG, you have to pass the following parameters in the "Parameters"-Field in the sensor's settings:

Just keep the "host" parameter as it is as it dynamically gets the IP-Address/FQDN from the parent device.

Hi John,

Thank you very much for providing the correction! I will edit the previous answer.

Kind regards
Andreas Günther, Technical Support

What would be very handy from PRTG would be a process based on the script above that replicated the wmi process monitor, so it displayed the same information :-)

Hello,

I'm attempting to run the following script from this thread but PRTG is throwing up an error XML: The channel name must not be empty. (code: PE242)

under settings for Sensor Display - Primary Channel I cannot select anything.

PRTG v18.2.40.1683 x64

Hi Andrew!

Could you please enable "Write Results to Disk" in the sensor's setting and forward us the logfile after waiting a few minutes? Please find the log in the folder "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)" on the probe, the sensor is running on. Please find the right files by looking for the numerical sensor ID in the filename. You can find the ID in the sensors "Overview" page on the right.

Please send us the files by email and enter "PAE1074576" in the subject line.

Thank you!

Andreas Günther
Tech Support, Paessler AG