A page view represents a user visiting a page from your website. During that page view, errors, resources, long tasks, and user actions get attached to that page view with a unique
view.id attribute. Note that a page view gets updated as new events are collected.
For Single Page Applications (SPAs), performance metrics will only be available for the first accessed page. Modern web frameworks like ReactJS, AngularJS, or VueJS update a website’s content without reloading the page, preventing Datadog from collecting traditional performance metrics. RUM is able to track page changes using the History API.
|number (ns)||Time when the browser first rendered any text, image (including background images), non-white canvas, or SVG.Learn more|
|number (ns)||The moment when the parser finished its work on the main document. More info from the MDN documentation|
|number (ns)||Event fired when the initial HTML document has been completely loaded and parsed, without waiting for non-render blocking stylesheets, images, and subframes to finish loading. More info from the MDN documentation.|
|number (ns)||The page and all the subresources are ready. For the user, the loading spinner has stopped spinning. More info from the MDN documentation|
|number (ns)||Event fired when the page is fully loaded. Usually a trigger for additional application logic. More info from the MDN documentation|
|number||Count of all errors collected so far for this view.|
|number||Count of all long tasks collected for this view.|
|number||Count of all resources collected for this view.|
|number||Count of all user actions collected for this view.|
Additional helpful documentation, links, and articles: