How Browser RUM Works
Browser RUM works in the following way:
- An end user requests the first page from your web application.
- Your web application executes whatever business logic that the particular page requires.
- Your web application creates the response page to return to the end user. The response page includes:
- application specific information
- As the page is being constructed in the browser, the script collects relevant information about the page's performance.
- At approximately the same time as the
- This second script packages the collected performance information and sends it via a web beacon to the EUM Server collector for processing.
- Working together the two scripts continue to collect and send performance information as the end user navigates through the instrumented pages of your application.
Not all types of injection are supported on all frameworks and platforms. See the Script Injection columns in the Supported Platform Matrix for Browser Monitoring matrices to find out what types are supported for your application.
adrum-xd.js. The first file is inserted into the page when it is downloaded from your web application. The second and third file are loaded asynchronously by the first. By default,
adrum-xd.js are fetched the highly available Amazon CloudFront CDN infrastructure.
cdn.appdynamics.com. This is the simplest hosting option and ideal for testing.
- Shared Hosting - You host the main file
Cross Domain Session Correlation
By default, Browser RUM sessions are restricted to one domain. Thus, when an end user navigates to a page in another domain or even subdomain, the session for that user is ended. You can, however, configure Browser RUM to enable sessions to continue across subdomains. Thus, when an end user navigates from
http://example2.com, the session will continue as long as the configured session inactivity time has not expired.
How Cross-Domain Sessions Are Correlated
For sessions to be correlated across domains, each page is required to use HTTPS to load the file
adrum-xd.html from the same URL. If your pages are fetching the files
adrum-xd.html files from the AppDynamics CDN (this includes the shared hosting use case), sessions will automatically be correlated across domains because the pages will be fetching the file
adrum-xd.html from the AppDynamics CDN.
adrum-ext.js file from the same URL. The
adrum-xd.html file is served from the location of the
adrum-ext.js file. See the sections below for configuration instructions for the two use cases.
Configuration for Cross-Domain Session Correlation
AppDynamics CDN / Shared Hosting
adrumExtUrlHttps is the same for all pages requiring cross-domain session correlation.
Alternate Geo Server Location
By default, end-users' locations are resolved using public geographic databases. You can host an alternate geo server for your countries, regions, and cities instead of using the default geo server hosted by AppDynamics. See Install and Host a Custom Geo Server for Browser RUM.
You can add configuration for