AppDynamics monitor

This section explains how to use the AppDynamics monitor. The AppDynamics monitor provides information on the availability and performance of software applications and the impact on user experience measured by the AppDynamics Platform, an application performance monitoring tool.

Prerequisites

Below is a list of prerequisites that are required to use this monitor:

  • You need to use a supported version of AppDynamics. For details, see the Integration with non-Micro Focus products section of the Support Matrix.

  • Since AppDynamics has solutions for on-premises or on the cloud, if you use a corporate proxy on your network, you need to set up a web proxy to collect data from it. To do so, on the LoadRunner Enterprise server, open the PCWEB\Web.config file in a text editor, and add the following under the configuration > system.net section of the file:

    <system.net>
      <defaultProxy enabled="true">
    <proxy proxyaddress="http://<PROXY_ADDRESS>:<PORT>" bypassonlocal="True" />
    </defaultProxy>
    </system.net>

Back to top

Set up the AppDynamics monitor

This task describes how to configure the AppDynamics monitor.

  1. From the LoadRunner Enterprise navigation toolbar, click and select Monitors (under Assets).

  2. In the test resource tree, select an existing monitor profile, or click New Monitor Profile and create a new monitor profile.

  3. In the Monitor Profile page, click Add Monitor and select AppDynamics.

  4. In the AppDynamics page, enter the server details:

    UI Elements

    Description

    Server

    The name or IP address of the AppDynamics server whose resources you want to monitor.

    Port

    The port number of the AppDynamics server.

    Default: 8090 for HTTP; 8181 for HTTPS

    Use HTTPS

    Specify if you are using a secure HTTP connection.

    Note: With some AppDynamics configurations, you might need to install SSL certificates on your AppDynamics server for it to work correctly. For details, see the AppDynamics documentation.

    User Name

    The monitored server's user name.

    Note: If in AppDynamics you are using an account name other than the default account (Customer1), you need to add the account name after the user name in the format: Username@accountname

    Password

    The monitored server's password.

  5. Click Get Applications and select the application that you want to monitor.

  6. Click Get Counters to display a list of available metrics and counters per metric from the selected AppDynamics application, and select the relevant measurements that you want to monitor.

    You can get all types of metrics including application, user experience, database, and server metrics.

    Note: Log details are available in Debug mode only. "Connection with AppDynamics" in logs is an 'Info' entry rather than 'Debug'.

    For detailed information on the performance measurements that AppDynamics can monitor, refer to the AppDynamics documentation.

Back to top

Configure additional AppDynamics monitor settings

You can make additional changes to the monitor’s behavior (on a per-machine basis) by editing the following settings in the AppDynamicsConfiguration.xml file (located in the <LoadRunner Enterprise Host install path>\dat\monitors directory):

  • HttpTimeout. Defines the timeout period, in milliseconds, for the HttpWebRequests. The default value is 15000.

  • MetricPollInterval. Defines the polling rate, in seconds, of the AppDynamics Controller. The default value is 60.

  • ValidateServerCertificate. Defines whether the SSL certificates on the host machine should be validated when using HTTPS. The default value is 0 for ease of use and broader compatibility. If you want stricter security control, change this value to 1. This requires you to install the AppDynamics certificates on the host machine.

Back to top

Notes and limitations

The following are notes and limitations for the AppDynamics monitor:

Delay displaying data

AppDynamics measurements appear in the LoadRunner Enterprise Run screen after a short delay. This is due to the way AppDynamics reports timestamps back to Controller, which are a few minutes behind the current time on the AppDynamics Controller machine.

When the test is started, the first timestamp and data-point reported are a couple of minutes old. As a result, it takes a few minutes of running before the Controller receives data-points that have timestamps which are valid for the test in progress.

No graphs displayed

When the selected counters in AppDynamics do not contain any data, the AppDynamics graphs might not appear in LoadRunner Enterprise.

Resolution: Check the AppDynamics dashboard to confirm whether the counters you selected contain data.

Back to top

See also: