Getting Started with RUM
RUM collects a large amount of data, which can be great, but also overwhelming. You might ask yourself: Where do I start? Which metrics are most appropriate for my properties? What do I do if I see something that looks problematic?
Before approaching these questions, it is recommended that you set up processes to support your RUM analysis goals.
|1. Start collecting RUM data.||While RUM starts collecting data after it is activated in the environment, you will need to collect weeks and months of data in order to notice trends.|
|2. Establish a Baseline.||Understand what constitutes “normal” for your properties.
For example, you may notice that response times consistently increase on Friday nights, which historically have been busy for your site(s). Or you may notice that your site performs better on certain types of browsers.
|3. Analyze your current pain points.||Generate Dimension reports to determine the time(s) that performance issues consistently occur for each URL you are monitoring. For more information, see Generating a Dimension Report.|
|4. Make note of upcoming releases/maintenance windows.||Keeping a calendar of upcoming releases can help determine whether performance issues are related to planned changes.|
|5. Set up your custom RUM metric groups.||RUM implementation allows you to set up
reports with the metrics most useful for your particular situation. |
For more information, see Creating Custom Metric Groups for more information.