4.2.x Documentation


PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
  • Created by Admin, last modified by Unknown User (ellen.evans@appdynamics.com) on Apr 04, 2016
Go to start of metadata

On this page:

Related pages:

You must have an EUM account and a Browser RUM license to access Browser RUM. See  EUM Account.

EUM must be enabled through the Controller GUI. You can enable and then disable EUM if you decide not to use the feature. See Enable and Disable EUM.

Metrics are collected on your end users' experience in their Web browsers using a special JavaScript for agent for Browser RUM. Your web application must be configured to insert this agent into the web pages it serves in order for them to monitored. This process is called injection. See Set Up Your Application for Browser RUM.

EUM Account

A special EUM account is required. An EUM account is created when you have a license for any of Browser RUM, Browser Synthetic, or Mobile RUM.  There is an account license key associated with this account. 

For on-premises customers, the account license key is set up within the Controller license file. If you added EUM after your initial installation, you may need to upload and install the new Controller license file. If you are a SaaS customer, the EUM license is set up in the SaaS Controller for you.

Each Browser RUM license provides a certain number of page views per year. For information on how to examine your current page view usage, see Browser RUM Licenses.

Accessing Browser Monitoring Configuration

Your data is displayed in the Controller UI in the context of an EUM application, which can be any name you choose.  An EUM application name is associated with an EUM App Key, which identifies data coming into the Controller.

  1. If you do not yet have an EUM application, click the User Experience tab, the Browser Apps tab and the +Add button.  You can create an application name either by using the Getting Started Wizard or by simply choosing an application name.
  2. Open the EUM application in which you are interested by double-clicking on the application name in the Browser Apps list.

  3. In the left navigation bar of the application UI, click Configuration.

Browser RUM Prerequisites

To turn on Browser RUM you need to:

  • enable End User Monitoring
  • inject the JavaScript agent into your application pages

Enable and Disable Browser RUM

  1. At the top of the configuration screen:
    • check Enable End User Monitoring to enable Browser RUM.
    • clear Enable End User Monitoring to disable Browser RUM.
       
  2. Click Save in the Browser Monitoring configuration screen after you have made your change.

Inject the JavaScript Agent for Browser RUM into Your Application Pages

The JavaScript agent for Browser RUM collects Browser RUM metrics. See Browser RUM Metrics for more detail.

The JavaScript agent for Browser RUM must be inserted into the headers of the pages for which you want to see these metrics. This process is called injection. There are several ways to accomplish this. See Set Up Your Application for Browser RUM.

Configure On-Prem Controller HTTP Proxy Settings (Optional)

If you have an on-premises Controller that uses an HTTP proxy host and port to communicate with the Internet, and you do not have an On-Premises EUM Server, you need to add the following JVM options to the Controller configuration so that the Controller can communicate with the EUM Cloud aggregator, which performs EUM data processing:

  1. Set appdynamics.controller.http.proxyHost to the proxy host name or IP address. 
  2. Set appdynamics.controller.http.proxyPort to the proxy HTTP port.
  3. If the proxy requires authentication, set credentials for the Controller using these options:  
    • Set appdynamics.controller.http.proxyUser to the user name that the Controller should use to authenticate to the proxy. 
    • Set appdynamics.controller.http.proxyPasswordFile to the plain text file that contains the password for the user. 

You can use the modifyJvmOptions utility to do this. Then stop and restart the app server.

For example, the following commands show how to modify the HTTP proxy options for a Controller on Linux. You must then stop and start the Controller's app server.

<Controller_installation_directory>/bin/modifyJvmOptions.sh add
-Dappdynamics.controller.http.proxyHost=myhost@-Dappdynamics.controller.http.proxyPort=8888
<Controller_installation_directory>/bin/controller.sh stop-appserver
<Controller_installation_directory>/bin/controller.sh start-appserver

Be sure to use the @ character to separate multiple options, as shown in the example. Alternatively, run the modifyJvmOptions utility once for each option to be added. 

The following commands modify the HTTP proxy options for a Controller that runs on Windows, then stops and starts the Controller's app server. The quotation marks enclosing the options string is required on Windows. Run the commands from an elevated command prompt, which you open by right-clicking on the Command Prompt icon in the Windows Start menu and choosing Run as administrator.

<Controller_installation_directory>\bin\modifyJvmOptions.bat add
"-Dappdynamics.controller.http.proxyHost=myhost@-Dappdynamics.controller.http.proxyPort=8888"
<Controller_installation_directory>\bin\controller.bat stop-appserver
<Controller_installation_directory>\bin\controller.bat start-appserver

If you need to modify these properties later, first run modifyJvmOptions with the delete command to delete the old setting, then use the add command to add the new ones.

To modify the Controller configuration file directly, use a text editor to change the domain configuration file: 

<Controller_installation_directory>/appserver/glassfish/domains/domain1/config/domain.xml

Add the following JVM option to the existing java-config element:  

<jvm-options>
     -Dappdynamics.controller.http.proxyHost=myhost
</jvm-options>
<jvm-options>
     -Dappdynamics.controller.http.proxyPort=8888
</jvm-options>

External Access Locations

Browser RUM is made up of several components, which, in various configurations, can either be located on the Internet or hosted inside your own data center/network.  On-premises access points are configured at installation or through the UI.  But if your installation requires access to any of these components on the Internet, the following is a list of the locations where the various components can be accessed. You need to make sure the appropriate URLs are accessible from your network.

  • Browsers download the JavaScript agent extension.  On the Internet, it is available from cdn.appdynamics.com
  • The JavaScript agent sends its data from the browser to the EUM Cloud.  On the Internet, the browser sends its beacons to col.eum-appdynamics.com.
  • The EUM Cloud sends analytics data to the Events Service.  On the Internet, the EUM Cloud sends its data to analytics.api.appdynamics.com:443
  • The Controller fetches data from the EUM Cloud.  On the Internet, the Controller fetches data from api.eum-appdynamics.com:443.
  • The Controller queries the Events Service.  On the Internet, the Controller queries analytics.api.appdynamics.com:443

Additional Browser RUM Configurations

You can also configure:


Have a question about the topic on this page? Ask the AppDynamics Community.