The following table provides frequently-asked questions (FAQs) about RUM.
|What data does RUM collect?||The RUM product uses the W3C’s Navigation
Timing specification, which provides an interface for browsers to expose data about an
individual page's performance. For a list of browsers that support Navigation Timing
see Navigation Timing API. |
|Does RUM collect personal data?||RUM collects data related to performance
timing, FEO utilization, and whether IPv6 was used for the session. |
Other dimension data used in RUM reports, like geography, IP address, browser type, and browser version, are already collected.
|What is the time lapse between turning on RUM and data appearing in RUM reports?||It currently takes up to 24 hours for RUM reports to generate data after an initial RUM configuration is activated on the network. This is based on the amount of traffic being sent, and time to populate the data in the portal.|
|How much RUM data do I want to collect?||For statistical relevance, your sample rate should produce at least 2000 beacons a day for the filters and URLs you care about looking at. If you are not receiving enough beacons, contact your account team for assistance.|
|How far back can I view report data?||At this time, RUM makes available 90 days
worth of data. Within this 90-day window, you can generate reports that have a date
range of 30 days or less.|
Note: You can use the export feature to save report data for future analysis. For more information, see Selecting Additional Filters for Your Pie Chart.
|Do you provide any guarantees on the availability of my RUM data?||At this time, there are no availability guarantees for RUM data.|
|How can I verify that the RUM configuration settings are working correctly?||The best way to verify that your RUM
configuration settings are working is by checking your RUM reports. |
|Does RUM replace Site Analyzer, or other synthetic test vendors for performance metrics?||No. Keynote and Gomez, as well as the Site Analyzer, generate synthetic Web page tests to determine baseline performance. This type of synthetic testing may not fully reflect an end user’s experience as they are usually run in a controlled environment on well-connected data centers, and use highly-customized browsers.
Because RUM data comes from users on a wide variety of hardware and network connections, you can expect to see variations. For example, a page could render in a few hundred milliseconds for one user on fast hardware and a high-speed connection, while the same page may take tens of seconds to render for a mobile user on a slow cellular connection.
By analyzing these users separately over a number of dimensions, the goal is to extract meaningful data that can provide insight into the actual end-user experience.
|Does RUM allow you to drill down to a single request?||No. Drilling down to a single data point is not useful when determining site performance, and goes against RUM’s sampling model, which is not designed for the 100% sampling rate this type of feature requires. For example, a single request may be slow because of the end user’s hardware, or because the end user is in an area with limited bandwidth.
However, if a problem is happening to 1% of requests on a busy production site, it could affect thousands of users. In this case, you can use your RUM data to determine whether the problem is directly related to your site.
For more information, see the use case, “My Customers Are Reporting Service Issues” on page 20.
|Are session attributes in cookies collected by RUM?||RUM does not collect any personal user information from cookies.|
|Can I export RUM data?||You cannot export raw RUM beacons.
However, you can export the data that creates the RUM reports you generate into either
CSV or a JSON file. |
For more information, see Exporting Your RUM Report Data.
|Can you generate a report based on an individual visit to the site?||At this time, the ability to generate a report based on an individual visit is not supported.|
|Can you trigger alerts through RUM?||At this time, triggering alerts through RUM is not supported.|
|Does RUM collect error condition data?||At this time, RUM does not collect error condition data.|
|Does RUM work on AJAX-enabled pages?||At this time, RUM does not monitor AJAX-enabled pages.|