Validate Changes to the Monitors Settings (Monitors Compatibility Tester)

The Monitors Compatibility Tester checks Aternity's advanced Monitors Settings window for Aternity on-premise deployments, to ensure that any manual changes comply to the rules for editing monitors in the system.

Tip

Use this tool to check the monitors after publishing any change to the monitors.

The Monitors Tester validates the following:

  • A process name must appear only once in all monitors of all managed applications in Aternity.

  • The URL for managed web applications must be properly formed.

  • You must remove any additional ‘enabler monitors’ which were added in the past for custom activities to capture HTTP, HTML or Java events. Aternity now has its own built-in enabler called Aternity Enabler.

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select the Gear Icon > Tools > Monitors Compatibility Tester.
  3. Step 3 Select Run Tests to verify Aternity's monitors.

    It creates a report listing the issues it found, organized like the Monitors Settings window, by application name.

    Validate the monitors in Aternity
  4. Step 4 To view the details of an error, hover your mouse over the item to see the details in a tool tip.
    Hover mouse pointer to view the details of each message
  5. Step 5 If several business applications use the same process:
    • You can display all the business applications as a single application in the dashboards, by adding the main application as managed, and then uploading the custom activities for all the business applications under the main application.

      For example if, MyMail's plugin does not have its own Windows process, you can add MyMail as a managed application, and include both its own activities and the plugin's activities all under a single application.

    • Alternatively, to display each business application separately in the dashboards, if you have custom activities defined for each business application:

    1. a Add one of the applications with its process name as a managed application.

      For example, if the applications bank_clients, bank_support and bank_vip all use the same underlying process bank.exe, create a managed application called bank_clients with the process bank.exe.

    2. b Add the remaining business applications as managed applications, but assign them a fictitious (dummy) process name.

      These act as containers to house the custom activities for each business application.

      For example, create additional managed applications called bank_support and bank_vip, each assigned with a made-up process name.

    3. c Upload custom activities for each business application.

      In this example, bank_clients would display usage and health data (like UXI, wait time, launch times) and the performance of its activities, while bank_support and bank_vip would display performance only in terms of their activity response times.