Add Multiple Process Names to a Managed Application

A Power User of Aternity can add more than one process to an application in the on-premise version of the system. Usually a monitored application runs just one Windows process (as it appears in the Windows Task Manager), like winword.exe. But if your application runs several processes, you should add all of them to the same monitor, so that Aternity can display the performance from all the processes under the same application name.

For example, SAP runs a number of Windows processes, including saplogon.exe, sapgui.exe and saplgpad.exe, but in the dashboards, all the performance activities should be displayed under the single application name, SAP. In other cases, applications (like Adobe Acrobat Reader) have different process names for their 32-bit and 64-bit variants.


All processes must have unique names in the entire system. The same process name should never appear in more than one application.

Only add extra process names belonging to the same application. Do not add a process name of a different application, even if this application launches another one.

For example, if you click on a link in an application and it opens spreadsheet, do NOT include the spreadsheet's process name within this application.

Before you begin

Before you add more than one process name for a monitored application, ensure you have done the following:

  • Add the application to be managed in Aternity by selecting the Gear Icon > Monitored Applications.


    Do NOT add a new application in the Monitor Settings screen. You must add it only in the Monitored Application screen, because there the system adds the required default settings which are essential to the smooth running of the dashboards.

  • Verify the access rights and privileges for your user includes Edit Monitors Tree privileges.

  • We recommend that at least one device in your organization is a monitored device, running the Aternity Agent, which gathers performance and usage data. See more on deploying the Agent on devices in your organization.

    You can only monitor applications on computers which have the Aternity Agent.


  1. Step 1 Open a browser and log in to Aternity.
  2. Step 2 Select the Gear Icon > Monitors to view the Monitors Settings tree.

    Do NOT change settings here unless you are an expert in Aternity, as it could easily ruin the data and dashboards of the system. Even then, only change the settings as prescribed in the official Aternity documentation.

  3. Step 3 Select the application you added which needs an extra process name.
    Find the application which needs more than one process

    Do not open, edit or remove these default monitors. They are essential for the proper monitoring of this application, and require their settings to remain untouched.

  4. Step 4 Add the extra process names by selecting + in the Process Names section, in the right hand pane.

    Each process name must be unique amongst all the monitored applications in Aternity.

    Adding multiple process names to a monitored application
    Field Description

    Select to monitor the launch time of this process. We recommend this only for processes which are launched as part of the start up of the application.

    Process Resources

    Select to monitor the CPU usage and other device resources used by this process.

    When the system monitors the CPU usage and other device resources of a Windows process (PRC), by default it checks this data hourly. If you want to change this setting as a Power User of Aternity, select the Gear Icon > Settings > Advanced Settings > agent > configuration > overrideConfigurationParam > Process resources > PrcFrequency > value and set the new value in milliseconds.

  5. Step 5 Select Publish in the top right corner of the page to commit the changes to the system and send them to the Aternity Agents on devices in the group you chose.
    Commit changes by publishing them

    Selecting Publish releases the editing lock on this screen and allows any other Power User of Aternity to edit the system's monitors.


    We recommend after changing the Monitors Settings, validate it by running the Monitors Tester.