Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Finding the process name associated with an application is often as simple as locating the application in the Windows Task Manager.

To find a Windows application's process name:

  1. Open Task Manager on the system that is running the application you want to monitor.
  2. On the Applications tab, right-click the application, and then click Go To Process on the context menu. The Task Manager should switch to the Processes tab and highlight the process belonging to the selected application.
  3. Make note of this process name as it

...

  1. is used when you configure the Process Count Check monitor.

If the application you want to monitor is running as a Windows service (i.e. as a background process), it will typically does not have a graphical front end and will does not appear as an application in the Task Manager.

To find a Windows service's process name:

  1. On the system that is running the application you want to monitor, open Services, which is accessed from the Administrative Tools Control Panel.
  2. Locate the service name (in the example below, it is Microsoft SQL Server Reporting Services).
    Image Modified
  3. Right-click the service name, and then

...

  1. click Properties. Locate the service's executable name in the Path to executable box (in this case, it is ReportingServicesService).
    Image Modified
  2. To verify that this service is running as a Windows process, open Task Manager, select the Processes tab, and then select

...

  1. the Show processes from all users check box. Confirm that the service executable is listed as a current process (in this case, ReportingServicesSerivce.exe is listed)

...

  1. .
    Image Modified
  2. Make note of this process name as it

...

  1. is used when you configure the Process Count Check monitor.

Identifying a UNIX process name

...

Given the less visibly direct association between UNIX processes and applications, you may need to use a utility to help you find the process you are looking for. Some examples include:

  • ps

...

  • . The process statistics command reports a snapshot of all currently running processes. For example, using

...

  • ps -ef

...

  • produces a full listing of every running process.
  • pstree

...

  • . This command is similar to ps except processes are displayed in a tree view. Using this command can help you determine which process is associated with an application by easily identifying parent processes. You can also add an application username as an argument to only display process trees that belong to applications initiated by the supplied user name.
  • pgrep

...

  • . This command expands on grep (which is used to find text in files based on a matching pattern) by finding processes based on attributes such as the executable's name. A regular expression that is supplied as an argument is matched against executable file names associated with running processes (e.g.

...

  • pgrep payroll$

...

  • returns all processes

...

  • with names

...

  • ending with "payroll"). If you have an idea of which application you are looking for, pgrep returns a relatively refined list of results and is an ideal method. 

Configuring the UIM Process Count Check monitor

To create a service in Uptime Infrastructure MonitorUIM

  1. Add a new service instance on the Services panel.
  2. In the Add Service Monitor window,

...

  1. in the Agent Monitors section, select the Process Count Check monitor. When configuring the monitor, make note of the Process Count Check Settings section.
    Image Modified
  2. In the Process Name box, enter the name of the process (or parent process) associated with the application that you want to monitor.
  3. In the Process Occurrences / Critical drop-down list, select is less than, then enter 0 in the box beside it.
  4. Continue to configure the service instance, making sure you also select a pre-defined alert profile. The alert profile

...

  1. determines how UIM reacts if the monitored application stops running.