On this page:
The sections below provide a high-level overview to checking your Browser RUM setup.
Make sure there is load running on your app for the pages that you want to monitor for the selected period.
When Browser RUM discovers a new page, iframe, or Ajax call for the first time, there will be a several minute delay before data for it appears in the Controller UI.
Confirm Browser RUM Is Enabled
Make sure you enable Browser RUM for the app. Enable it if it is disabled. See Enable and Disable Browser Monitoring.
Examine the source of your web page to ensure that you have instrumented the pages that you want to monitor.
Make sure there is connectivity from the browser to the EUM Cloud. See Connection Problems for information about troubleshooting connectivity.
If beacons are not present or their status is not valid, verify your Browser RUM configuration. See Set Up and Access Browser RUM.
To examine your instrumented application for issues, verify the following:
adrum.ext) is loaded and its status is OK (200).
adrum.gifis loaded, and its status is OK (200).
ky parameter in the beacon is set to your application key.
Beacons for using image requests have an inherent length limitation. Because of this, URLs longer than 180 characters, page names longer than 50 characters, and user data (key and value combined) longer than 113 characters are not supported in these browsers.
You can use the developer tools in your web browser to examine your application.
This screenshot shows a
.gif-based beacon in Chrome.
This screenshot shows a CORS-based beacon with a key in the URL path.
Create a HAR file to confirm that the browser is downloading the expected resources for your web page.