FAQ

Route change definition

We rely on router libraries (such as ui.router or ngRoute if you're using AngularJS) to detect route changes. This is of course after the framework (e.g. AngularJS) has loaded in the page and has initialised your application. Furthermore we keep track of async tasks (such as XHR) during a route change, so we consider a route change as finished only when all of the tasks related to it are finished.

Initial page load events

We capture all events from window.performance.timing, However we only group some of them into traces in your dashboard. Here are the events and their trace name:

• domainLookupStart, domainLookupEnd --> 'DNS lookup'
• connectStart, connectEnd --> 'Connect'
• requestStart, responseStart --> 'Sending and waiting for first byte'
• responseStart, responseEnd --> 'Downloading'
• domLoading, domInteractive --> 'Fetching, parsing and sync. execution'
• domContentLoadedEventStart, domContentLoadedEventEnd --> '"DOMContentLoaded" event handling'
• loadEventStart, loadEventEnd --> '"load" event handling'

cross-origin issue

Other than Setting up CORS, you should add crossorigin attribute to all of the script tags that you want to log errors from and are loaded from a separate domain.