Integrate with SteelCentral 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 SteelCentral AppInternals™. In AppInternals you can trace an activity's call (AppInternals 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 AppInternals

You can switch to AppInternals from the top bar of Aternity, or you can drill down to AppInternals 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 any version of AppInternals released in the last five years, both SaaS and on-premise.

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

  • You must be able to sign in to both SteelCentral Aternity™ and SteelCentral 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 AppInternals 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 AppInternals in the SteelCentral AppInternals™ section.
    Configure Aternity to point to AppInternals
    Field Description
    SteelCentral AppInternals™

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

    (AppInternals SaaS only) Add the realm ID (or customer id) after the domain, in the format of https://steelcentral.net/?realm=<realm_id>. You can see the ID in AppInternals by navigating to Configure > Install Agents and copying the Customer id.

    Find your realm id in AppInternals
    Tip

    To quickly switch back to Aternity from AppInternals with the link in the top bar, this URL should be external, visible to the Aternity SaaS system in the cloud.

  4. Step 4 Access AppInternals from a web browser.
  5. Step 5 Configure your AppInternals 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 AppInternals 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 AppInternals 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 AppInternals monitors all AJAX calls (except for Android monitored mobile apps).

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

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

    Move between Aternity and AppInternals
  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 SteelCentral 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 AppInternals to monitor each call to a server's back end components.

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

      Drill down to view this transaction in AppInternals
      Field Description
      View Transactions in AppInternals

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

      View Pages in AppInternals

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

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

      For more information, see the online help for AppInternals.

      View server side details of the transaction