Interpreting the trigger event result

Depending on the performance type and options selected for monitoring, the JSON string returned by the .result method contains the following information:

For CPU performance type

• ComputerID - the name of machine that logged the trigger event.
• reportCollectedDateTime - the local time stamp of the beginning of monitoring (that is, when the performance activity started running).
• ComputerDuration - the amount of time it took for the trigger to execute (that is, how much time has passed since the monitoring started and until performance thresholds were exceeded).
• PercentValue - the CPU value logged at trigger execution time, for the selected application (that is, what was the CPU value when the trigger executed).

• Process - an array displaying information about the monitored application. If you are monitoring the entire system, the array displays information on all processes consuming more than 0.01% of the monitored resource:

  • ProcessName - the name of the corresponding process (that is, the application name as found in Windows Task Manager > Details tab)
  • ApplicationName - the name of the application (that is, the application name as found in Windows Task Manager > Apps)
  • PercentValue - the CPU value logged at the moment of displaying the result, which may be different from the value that caused the trigger to execute.

For Memory performance type

• ComputerID - the name of machine that logged the trigger event.
• reportCollectedDateTime - the local time stamp of the beginning of monitoring (that is, when the performance activity started running).
• ComputerDuration - the amount of time it took for the trigger to execute (that is, how much time has passed since the monitoring started and until performance thresholds were exceeded).
• PercentValue - the memory percentage logged at trigger execution time, for the selected application (that is, what was the memory percentage value when the trigger executed).

• Process - an array displaying information about the monitored application. If you are monitoring the entire system, the array displays information on the top ten consuming processes:

  • ProcessName - the name of the corresponding process (that is, the application name as found in Windows Task Manager > Details tab)
  • ApplicationName - the name of the application (that is, the application name as found in Windows Task Manager > Apps)
  • PercentValue - the memory percentage used by the application, logged at the moment of displaying the result, which may be different from the value that caused the trigger to execute.
  • MemoryValue - the memory value in MB logged at the moment of displaying the result.

For Disk performance type

• ComputerID - the name of machine that logged the trigger event.
• reportCollectedDateTime - the local time stamp of the beginning of monitoring (that is, when the performance activity started running).
• ComputerDuration - the amount of time it took for the trigger to execute (that is, how much time has passed since the monitoring started and until performance thresholds were exceeded).
• PercentValue - the disk percentage logged at trigger execution time, for the selected application (that is, what was the disk percentage value when the trigger executed).

• Process - an array displaying information about the monitored application. If you are monitoring the entire system, the array displays information on the top ten consuming processes:

  • ProcessName - the name of the corresponding process (that is, the application name as found in Windows Task Manager > Details tab)
  • ApplicationName - the name of the application (that is, the application name as found in Windows Task Manager > Apps)
  • PercentValue - the disk percentage used by the application, logged at the moment of displaying the result, which may be different from the value that caused the trigger to execute.

For Network performance type

• ComputerID - the name of machine that logged the trigger event.
• reportCollectedDateTime - the local time stamp of the beginning of monitoring (that is, when the performance activity started running).
• ComputerDuration - the amount of time it took for the trigger to execute (that is, how much time has passed since the monitoring started and until performance thresholds were exceeded).
• PercentValue - the network percentage logged at trigger execution time, for the selected application (that is, what was the network percentage value when the trigger executed).

• Process - an array displaying information about the monitored application. If you are monitoring the entire system, the array displays information on the top ten consuming processes:

  • ProcessName - the name of the corresponding process (that is, the application name as found in Windows Task Manager > Details tab)
  • ApplicationName - the name of the application (that is, the application name as found in Windows Task Manager > Apps)
  • PercentValue - the network percentage used by the application, logged at the moment of displaying the result, which may be different from the value that caused the trigger to execute.
  • NetworkValue - the network value in bps logged at the moment of displaying the result.

For child processes

For trigger events with the Include child processes option selected, the JSON string includes an additional array for each Process item. The Child Process array contains the following information:

• PID - the process identification number, as shown in the Windows Task Manager > Details tab.

• ProcessValue - the value of the child process, as follows:

  • CPU - the child process percentage as a decimal value (that is, the percentage value divided by 100);
  • Memory - the child process memory value in MB logged at the moment of displaying the result;
  • Disk - the total value of system disk input/output operations in bytes. This value is the same for all child processes.

• ProcessPercentage - the percentage used by the child process.

  For example, a parent process has two child process and its PercentValue is 3,5%. One child process has a ProcessPercentage value of 2,0%, while the second child process has a ProcessPercentage value of 1,5%, together summing up to the parent process percentage usage.

• Title - the name of the child process, as displayed in the UI, if available.