if your pageRequest contains an automation overseerScript, it's output will be here. see IPageRequest.overseerScript for details
runtime errors unhandled by the content will be shown here
cookies set at the moment the IPageRequest transaction completed.
new for Chrome backend. information on what finished the page execution. In addition to pageExecLastWaitedOn, eventPhase and resources, this is useful for debugging your requests.
any errors raised during page execution will be shown here
new for Chrome backend. information on what event phase the page was in when it finished processing. In addition to pageExecLastWaitedOn, doneDetail and resources, this is useful for debugging your requests.
events that occured during requesting and loading of the IPageRequest and it's content
the Frames contained in the page. The first is always the main page itself, even if no other frames are present.
headers for the primary resource (the url requested). for headers of other resources, inspect the pageResponse.events (key='resourceReceived')
information about the processing of your request
new for Chrome backend. displays the last thing that the page execution subsystem was waiting on. In addition to doneDetail and resources, this is useful for debugging your requests
the request you sent, including defaults for any parameters you did not include
new for Chrome backend. details all resource load times, ordered by when they started. This aggrigates resource details from events into an easy to read format. In addition to doneDetail, eventPhase and pageExecLastWaitedOn, this is useful for debugging your requests.
Provides the following details:
elapsed: how long the resource took to load in ms
detail: details on the resource's ending state. format is STATE.STATUSCODE.STATUSMESSAGE
complete, active (was still loading when the page finished), late (was still loading, and took longer than IRequestSettings.resourceWait allows), or killed (took longer than IRequestSettings.resourceTimeout allows so was aborted).504. If an error occured without a response from the remote server, status 502 is used.start: the time in ms since page started execution, and what phase the page execution was in when the resource was requested:
initialRequest: the first resource has not finished yet.pageNavigated: the dom has not finished loading yet (page is usually blank at this point).domReady the dom is loaded and you can visually see the page, but it's not done yet.load: the page is considered complete.ended: the time in ms since page started execution, and what phase the page execution was in when the resource was finished. see started for a description of these phases.
If the resource did not finish you will see a time of Infinity and phase of (undefined).
frame: the frame requested the resource (last 4 digits of it's frameId). if it's the main frame, we put "main" as it's name. additionally, if the request was a navigation of the frame, (nav) is added.
type: the type of the resource: document | stylesheet | image | media | font | script | texttrack | xhr | fetch | eventsource | websocket | manifest | other
url: the url of the resource. if it's longer than 100 characters, the first and last 50 characters will be shown.
run a script and direct output to
the status code for the page, a shortcut to metrics.targetUrlReceived.value.status
Information about the IPageRequest transaction (request and it's response).