Configure Advanced Monitor Settings for Applications

After adding an application to be managed by the system, you can configure advanced monitoring properties for those applications in the on-premise version of the system.

Configure advanced settings for managed applications in the monitors tree

The monitors tree shows the managed applications, their defined monitors, and their activities.

To... Do This...

To add a custom activity to Aternity on-premise

Upload a signature file which contains the details of that activity in XML.

For more information, see Upload a Custom Activity to Aternity.

To add more than one process to an application in the on-premise version of the system

See Add Multiple Process Names to a Managed Application.

To change the SLA thresholds for an activity

See Set the SLA thresholds of an Activity.

To change the baselines and detection for an activity

See ~Baseline Settings~.

To view the complete set of data collected by Aternity monitors

See View Data Monitored by Aternity.

Before you begin

Before you configure any advanced monitor settings in Aternity, ensure you have done the following:

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

    Important

    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.

Procedure

  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.
    Important

    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 To upload a custom activity to an application, see Upload a Custom Activity to Aternity.

    A Power User of Aternity can add a custom activity to Aternity on-premise, by uploading a signature file which contains the details of that activity in XML.

  4. Step 4 To add more than one process name to a monitor, see 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.

  5. Step 5 To define the SLA thresholds for an activity, see Set the SLA thresholds of an Activity.
    Set the external and internal thresholds for an activity's SLA

    An SLA threshold is the activity response time specified in your service level agreement (SLA). The application provider commits as part of their service that it performs smoothly for everyone by assuring that all its activities respond within certain performance times. There are two types of SLA thresholds: internal and external.