Integrate with Aternity APM (previously AppInternals) to Troubleshoot Server Times

Troubleshoot a long backend time (part of a slow response time) of a user's activity, by drilling down from the activity into Aternity APM (previously AppInternals). In Aternity APM you can trace an activity's call (APM transaction) to the server as it crosses the server-side components, and follow it across the backend components. If the activity makes two calls to the same server, or to two different servers, you can drill down from this activity to trace two separate transactions.

Troubleshoot a slow backend time by drilling down to Aternity APM

You can switch to Aternity APM from the top bar of Aternity, or you can drill down to Aternity APM to trace all transactions from one activity, or to follow all transactions found in the same instance of a web page.

Example tracing a user experience slowdown to specific server code methods

Before you begin

You can only monitor an activity all the way from the device side to its server-side transactions if you have all the following in place:

  • You must have Aternity on-premise v10.x or later, and any version of Aternity APM released in the last five years, both SaaS and on-premise.

    Aternity does not communicate directly with Aternity APM, but rather offers a URL to view the transaction there. Therefore you do not need a direct port open between Aternity and Aternity APM.

  • You must be able to sign in to both Aternity and Aternity APM (previously AppInternals).

  • The application must be managed in Aternity, and it must already have a custom activity. It can be:

  • The user must perform an activity on a monitored device which runs Agent for End User Devices 9.2 or later, or from a mobile app with Aternity monitoring embedded using Aternity Mobile 9.3 or later.

  • You must install the Backend Agent on all target servers on the back end of this activity. This allows Aternity APM to trace a transaction's path across the servers.

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select the Gear Icon > Integration Settings.
  3. Step 3 Point Aternity to your Aternity APM in the Aternity APM (previously AppInternals) section.
    Configure Aternity to point to Aternity APM
    Field Description
    Aternity APM (previously AppInternals)

    Enter the front-end URL of your Aternity APM server (Analysis Server), either SaaS or on-premise.

    Find your realm id in Aternity APM
    Tip

    To quickly switch back to Aternity from Aternity APM with the link in the top bar, this URL should be visible from the Aternity Management Server.

  4. Step 4 Access Aternity APM from a web browser.
  5. Step 5 Configure your Aternity APM for optimum integration with Aternity, so that Aternity can associate transactions and web pages with the widest possible range of client-server traffic.

    Select Configure > Configurations > Default configuration or select the custom configuration for the processes you want to monitor.

    Configure Aternity APM for the best integration with Aternity

    Select the following fields (if not already selected) in the Data Collection Settings > Custom section.

    Field Description
    Collect End-User Experience Data

    Select this for Aternity APM to inject its JavaScript, which Aternity uses to track the ID of a web page and transaction.

    Customize Snippet > AJAX > Synchronously load JavaScript library for AJAX pages

    Select this to ensure Aternity APM monitors all AJAX calls (except for Android monitored mobile apps).

  6. Step 6 To quickly switch to Aternity APM, select Switch to Aternity APM from the top bar of any page in Aternity.

    Use the Switch to Aternity APM and Switch to Aternity links to see the information you need for troubleshooting.

    Move between Aternity and Aternity APM
  7. Step 7 In Aternity, access the Monitor User Experience dashboard of the user or device which performed the activity.

    Type the username or hostname in the top bar's search box.

  8. Step 8 Troubleshoot a long backend time (part of a slow response time) of a user's activity, by drilling down from the activity into Aternity APM (previously AppInternals).
    1. a Identify an activity which contacted one or more servers, which is slow due to a long backend time.

      Hover your mouse over an activity whose status is major () to view the breakdown of its client, network and backend time. Check if the backend time is the main culprit for the slow response time.

      Identify an activity whose backend time needs investigating
    2. b Drill down to Aternity APM to monitor each call to a server's back end components.

      This requires you to sign in to Aternity APM. To sign in to Aternity APM SaaS with SSO, it must use the same identity provider as that configured for Aternity.

      Drill down to view this transaction in Aternity APM
      Field Description
      View Transactions in Aternity APM

      Select to drill down to Aternity APM to view the transactions resulting from this activity's call to the server.

      View Pages in Aternity APM

      If an activity occurs on a web page, you can drill down to Aternity APM to view the transactions plus all other transactions which originated from that instance of the web page.

    3. c Select View transaction details in Aternity APM to narrow down the segment of the transaction which caused the delay in backend time.

      For more information, see the online help for Aternity APM.

      View server side details of the transaction