How To View Server Top Processes in DPACK Project
DPACK collectors will being recording a list of top processes running on the servers that it monitors. This will provide users insight into the application workload on a given server.
A running process is an application or service running on the server.
DPACK will record usage statistics for the running process. This usage will include CPU time, disk IO, hard page faults, and private (non-shared) memory usage.
Currently, DPACK will only collect and list the top running process on Windows and Linux based operating systems. For an other OS (Solaris, HP-UX, and ESXi), this information will not be collected, nor will it display any information within this list.
The following steps detail how to access the top application processes output DPACK collected for each applicable device during the collector run.
- The DPACK project has already been created from one or more DPACK collector runs
- Access to a DPACK account should already be complete before beginning the following steps.
Step 1: Access Performance View of project
- Locate project to view and click on the name at the top
- Once the project opens, click on the Performance View tab
Step 2: Select server in device list
The Top Processes list is only for an individual device in a DPACK project and cannot be viewed from when looking at the aggregate information. Select a server from the device list.
Step 3: Select Installed Applications button
To view the list of top processes on a server, click "Top Processes". By default, the top processes are listed by those using the largest amount of CPU time. There are three other sorting criteria that can be used to list top processes. They are disk read time (Reads), disk write time (Writes), and memory usage (Memory). Anytime a new sorting button is selected, the data will automatically change and display a new list of processes.
If at anytime you want to view the top processes on another server in a DPACK project, select a new server from the Device List and a new list of processes will be generated.
- When DPACK is collecting application process data, it is looking at the following information:
- Process Name: Often times, this will be listed as the EXE file running for a process. In the case of a Windows Service, this name will include an appended list of service names that share the process shell.
- CPU Percentage since last boot
- Disk Reads
- Disk Writes
- Hard Page Faults
- Memory Usage: This does not include any shared memory usage between application
- The discovery of application information occurs during the initial DPACK discovery phase, prior to the start of the DPACK capture. Any processes starting after DPACK discovery could be missed during the analysis of top running processes.