After applying a time range on the top right, you can find events with key:value pairs and a full-text search in the RUM Explorer.
While RUM automatically captures events, you can also capture your own events. All auto-captured and custom events are stored into six event types for browser, iOS, Android, and React Native applications and indexed to become searchable.
| Event Type | Retention | Description |
|---|---|---|
| Session | 30 days | A user session begins when a user starts browsing the web application. It contains high-level information about the user (such as browser, device, and geolocation). It aggregates all RUM events collected during the user journey with a unique session.id attribute. |
| View | 30 days | A view event is generated each time a user visits a page of the web application. While the user remains on the same page, resource, long-task, error, and action events are linked to the related RUM view with the view.id attribute. |
| Action | 30 days | RUM action events track user interactions during a user journey and can be manually sent to monitor custom user actions. |
| Error | 30 days | RUM collects every frontend error emitted by the browser. |
| Resource | 15 days | A resource event is generated for images, XHR, Fetch, CSS, or JS libraries loaded on a webpage. It includes detailed loading timing information. |
| Long Task | 15 days | A long task event is generated for any task in the browser that blocks the main thread for more than 50ms. |
To search through your RUM events, select an event type from the dropdown menu to the left of the search bar.
To filter on sessions produced by a specific application by real users over the past day, create a custom query such as @application.id:Shopist @session.type:user and set the time range to 1d.
Note: If you are including a facet in your query, be sure to create the facet first.
For more information about searching for RUM events and using time frames, see Search Syntax and Custom Time Frames.
All RUM events contain attributes, which are automatically collected by the RUM SDKs, and your custom attributes, which are displayed on the event side panel.
While most automatically collected attributes are indexed and faceted, your custom event attributes are not indexed and faceted by default. Index these attributes by creating a facet or measure to be able to access them in your search and visualizations.
A facet displays all distinct members of an attribute or tag and provides basic analytics, such as the number of RUM events represented. Facets allow you to pivot or filter your datasets based on a given attribute. Selecting a value applies a filter in the search bar.
To create a facet, find and click on an attribute in the event side panel.
The value for the attribute is stored across all new views. You can access these attributes in the search bar, the Facets panel, and your visualizations.
A measure is an attribute with a numerical value contained in your RUM events.
To create a measure, find and click on a numerical attribute in the event side panel.
The value of this attribute is stored across all new RUM events. You can access these attributes in the search bar, the Facets panel, and your visualizations.
Every measure has a unit that is displayed in a column of the RUM Explorer and in your visualizations.
To search for a specific attribute, add it as a facet and enter @ in your search query. This specifies that you are searching for a facet.
For example, if your facet name is url and you want to filter on the url value www.datadoghq.com, enter @url:www.datadoghq.com.
Additional helpful documentation, links, and articles:
