You must have an EUM license to access Web EUM. See EUM License.
End User Monitoring (EUM) must be enabled at the application level. Its UI is visible in the Controller GUI only if EUM is enabled. You can enable and then disable EUM if you decide not to use the feature. See Enable and Disable EUM.
A special EUM license key is required. It covers both Web EUM and Mobile EUM.
For on-premise customers, the license key is set up within the Controller license file. If you added EUM after your initial AppDynamics installation, you may need to upload and install the new Controller license file. See Controller Licenses. If you are a SaaS customer, AppDynamics sets up the EUM license in the SaaS Controller for you.
Accessing Web EUM Configuration
Select the application for which you wish to enable EUM.
To create a new application manually:
- Log into the controller with your AppDynamics credentials.
- In the left navigation pane click Applications.
- In the right pane Click + Create Application.
- Enter a name and optional description for the mobile application that you will instrument.
- Click OK.
- In the left navigation menu, click Configure -> Instrumentation.
Click the End User Experience tab.
Always remember to click Save in the EUM configuration screens whenever you make a change.
Web EUM Prerequisites
To turn on Web EUM functionality you need to:
- enable End User Monitoring
Enable and Disable Web EUM
- At the top of the End User Experience configuration screen:
- check Enable End User Experience Monitoring to enable Web EUM.
- clear Enable End User Experience Monitoring to disable Web EUM.
- Click Save in the Web EUM configuration screen after you have made your change.
Configure On-Prem Controller HTTP Proxy Settings (Optional)
If you have an on-premise Controller that uses an HTTP proxy host and port to communicate with the Internet, 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:
- Set appdynamics.controller.http.proxyHost to the proxy host name or IP address.
- Set appdynamics.controller.http.proxyPort to the proxy HTTP port.
- New in 3.8.2 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, then stop and start the Controller's app server.
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.
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 delete the option, specify both the key and value of the key. See Modify GlassFish JVM Options for details.
To modify the Controller configuration file directly, edit the domain configuration file:
Add the following JVM option to the existing java-config element:
Additional Web EUM Configurations
You can also configure:
- Page Identification and Naming
- Browser Snapshot Thresholds
- Browser Snapshot Collection Rules
- Deployment Customization