When monitoring a process using processes probe, you may notice a weird metrics value (-1) on a custom dashboard:
In the log file, you may also notice the following log messages:
Jun 20 17:58:53:791 processes: Leaving the GetProcessCmdLine function
Jun 20 17:58:53:791 processes: PID: [3876] ReadIODiskBytes: [4]
Jun 20 17:58:53:791 processes: PID: [3876] WriteIODiskBytes: [38]
Jun 20 17:58:53:791 processes: PID: [3876] OtherTransferCount: [0]
Jun 20 17:58:53:791 processes: (DiscoverProcesses) - Arguments copied to BinPath
Jun 20 17:58:53:791 processes: Finding information about process no 52 pid=3964...
Jun 20 17:58:54:028 processes: Hang_Issue After ciOpenLocalDevice Line number : 23 , Function_Name : nimQoSMessageWrapper
Jun 20 17:58:54:028 processes: (QOS_PROCESS_MEMORY) QoS Create Success
Jun 20 17:58:54:028 processes: (QOS_PROCESS_MEMORY) CiOpenLocal Device Success.
Jun 20 17:58:54:029 processes: RREPLY: status=OK(0) <-IP_ADDRESS:port h=37 d=28
Jun 20 17:58:54:029 processes: ciClose - [C401A69DBF7F50DD78FD874C558EC928C]
Jun 20 17:58:54:029 processes: sockClose:000001B8AB3BE020:IP_ADDRESS:port
Jun 20 17:58:54:029 processes: SREQUEST: _close ->IP_ADDRESS:port
Jun 20 17:58:54:030 processes: Hang_Issue Before nimQoSMessageWrapper Line number : 1855
Jun 20 17:58:54:030 processes: Sent QOS_PROCESS_MEMORY -1 for lsass
Release : 20.4.x
Processes version : 4.82
Code defect
The new version of the processes probe has been released (4.82 T1)