Browser RUM works in the following way:
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.html. The first file is inserted into the page when it is downloaded from your web application. The second and third files are loaded asynchronously by the first. By default,
adrum-xd.html are fetched the highly available Amazon CloudFront CDN infrastructure.
cdn.appdynamics.com. This is the simplest hosting option and ideal for testing.
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.
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.
adrumExtUrlHttps is the same for all pages requiring cross-domain session correlation.
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