RUM Analytics

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Overview

Real User Monitoring (RUM) Analytics extend the RUM Explorer page with views data aggregation and split capabilities for troubleshooting and monitoring. You can control:

The query that filters the set of views to analyze.
The dimensions over which to split data.
The visualization method for aggregates and splits.

From an analytics visualization, you can, additionally:

Create a widget in a dashboard out of that visualization.
Dive deeper into subsets of the events list, depending on the interactions that the visualization enables.

Build an analytics query

Use the query to control what’s displayed in your RUM Analytics:

Choose a measure or facet to graph. measure lets you choose the aggregation function whereas facet displays the unique count.
Select the aggregation function for the measure you want to graph:
Use a facet to split your graph.
Choose the time interval for your graph. Changing the global timeframe changes the list of available timestep values.
Choose to display either the X top or bottom values according to the selected measure.

Visualizations

Select a RUM Analytics visualization type using the graph selector:

Available visualizations:

Dropdown

Visualize the evolution of a single measure (or a facet unique count of values) over a selected time frame, and (optionally) split by an available facet.

You have additional display options for timeseries:

Whether you display lines, bars, or areas.
Data stacking option: by value or by percentage.
Color set.

Noteworthy facts about stacking:

Stacking is available only for query requests with a split.
Stacking options are for bar and area displays only. Line displays are always overlapping.
When you use a toplist option that hides part of your data, stacking does not show the total overall; rather, it shows only the subtotal for the top/bottom series.
Stacking may not make sense when you have non-unique values in the split facet.
Stacking may not make sense for some aggregation methods for measures.

The following RUM Analytics timeseries shows:

The evolution of the Browser Family according to the 90th percentile of DOM interactive time over the last 7 days.

Visualize the top values from a facet according to the chosen measure:

The following RUM Analytics Top List shows:

The evolution of the top 10 URL Paths according to the number of unique Sessions ID over the last day.

Visualize the top values from a facet according to a chosen measure (the first measure you choose in the list), and display the value of additional measures for elements appearing in this top value. Update search query or drill through events corresponding to either dimension.

When there are multiple dimensions, the top values are determined according to the first dimension, then according to the second dimension within the top values of the first dimension, then according to the third dimension within the top values of the second dimension.
When there are multiple measures, the top or bottom list is determined according to the first measure.
The subtotal may differ from the actual sum of values in a group, since only a subset (top or bottom) is displayed. Events with a null or empty value for this dimension are not displayed as a sub-group.

Note: A table visualization used for one single measure and one single dimension is the same as a toplist, just with a different display.

The following RUM Analytics table shows the top 5 URL path for two countries: US and Japan consulted according to their amount of Unique Session ID, along with the 90th percentile of Duration, and over the last day: