GENEOS Top Plug-in monitors systems for resource hungry tasks.
It works by displaying processes that breach a configurable threshold value (e.g. 20% CPU usage).
Processes are said to be in breach when they exceed the threshold value and, optionally, are in the top N processes to exceed the threshold; where N is a configurable value (maxRows). The plug-in can also display processes that were recently in breach. These are referred to as tailed off and are displayed for a tail off period.
The plug-in produces a single view. This will display two headline variables, a summary of the breach condition and the number of processes currently in breach. The table displays processes in breach and, if a Tail Off Period is specified, processes recently in breach. Column values are configurable except for the first column name, which always displays the processes name and PID.
The view can be configured on the Advanced tab > Process parameters to display any of the columns listed below.
|A summary of what is being displayed
|The number of breached processes being displayed
|The name of the process and the PID. This creates a unique identifier for the process.
|% of recent cpu used by this process instance.
|Virtual memory size of this process instance.
|Resident set size of this process instance.
|The Unix PID number of this process instance.
|The PID number of the parent process.
|The command line arguments of this process instance.
|% of memory occupied by this process instance. (UNIX only)
|The time this process instance started. (UNIX only)
|The User that started this process instance. (UNIX only)
|The Unix Groupid of this process instance. (UNIX only)
|Number of threads being used by this process instance. (UNIX only)
|The current state of this process instance e.g Running, Sleeping etc. (UNIX only)
|The number of hours that the process has been running. (UNIX only)
|The number of days that the process has been running. A process started at one minute to midnight will show as as 1 day at one minute past midnight, even though AgeHours will be 0. (UNIX only)
|The number of file descriptors held by the process. (UNIX only)
|Cumulative CPU time used by the process in a human readable format. (Solaris only)
|Cumulative CPU time used by the process in seconds. (Solaris only)
|% of recent user time used by this process instance. (Windows only)
|% of recent privileged time used by this process instance.
|(Windows only) virtualMemPeak
|Peak virtual memory size of this process instance. (Windows only)
|Page faults per second caused by this process instance. (Windows only)
|Peak resident set size of this process instance. (Windows only)
|Peak page file bytes used by this process instance. (Windows only)
|Page file bytes used by this process instance. (Windows only)
|Base priority of process. (Windows only)
|Number of seconds elapsed since the process started. (Windows only)
|Number of bytes in the Paged Pool (Windows only)
|Number of bytes in the Nonpaged Pool, (Windows only)
|Number of handles held by process instance. (Windows only)
|Number of GDI objects held by process instance. (Windows only)
|The User that started this process instance. (Windows only)
Plug-in Configuration Copied
Defines the parameters (process attributes) to be shown for each process monitored. To disable this mode, set the environment variable SOLARIS_OS_DIRECT to FALSE in the start_netprobe script.
The available process parameters for Unix are:
|% of recent cpu
|% of system memory
|Virtual memory size
|Resident set size
|Parent process id
|Command line args
|Number of threads
|Process state, running, sleeping etc.
|Age of the process in hours
|Age of the process in days
|The cumulative CPU time of the process in the form [[dd-]hh:]mm:ss (Solaris Only)
|The cumulative CPU time of the process in seconds (Solaris Only)
Additionally, the following process parameters are available on Linux:
|Major Page Faults per second
|Total Major Page Faults
|Number of Dirty Memory Pages
The available process parameters for Windows are:
|% of recent cpu
|% user time
|% privileged time
|Virtual memory size
|Virtual bytes peak
|Page faults per sec
|Working set peak
|Page file bytes peak
|Page file bytes
|Pool paged bytes
|Pool non paged bytes
|Creating process id
|Command line args
NoteFor fd usage: If the NetProbe doesn’t have root permissions it will only be able to read file descriptor counts for processes running as the same user as the NetProbe.
Default: pcpu, vsz
threshold > thresholdParameter Copied
Defines the parameter which is tested against the threshold value to determine if processes are in breach. Can be defined as any numeric processParameter.
threshold > greaterThanOrEqualTo Copied
Sets threshold test type to Greater Than Or Equal To. Contains a decimal value.
threshold > lessThanOrEqualTo Copied
Sets threshold test type to Less Than Or Equal To. Contains a decimal value.
Defines the optional Tail Off Period for which processes remain displayed after they are no longer in breach of the threshold value, this is in order to aid logging cells to a database. If set to zero, processes cease to be displayed the moment they are out of breach.
Value is in seconds.
Defines an optional maximum number of breached processes to display.
If this field is used in conjunction with Less Than Or Equal To, then the plug-in sorts the rows in the dataview according the processes with the least HandleCount values, before limiting the number of rows accordingly.
Adjusts the percentCPU of each process by taking the percentage of time being used by the process and then dividing by the number of cores/cpus on the machine. For example, suppose we have a process using up 10% of 1 core on a 4 core box. If this setting is enabled, then we would expect the dataview to display this process as using 2.5% instead. If this setting is not enabled then we would expect 10% to be displayed as usual.