New Relic Synthetics automatically records each monitor check, allowing you to see the load time and response size for every run. For simple browser and scripted browser monitors, Synthetics also records a detailed "waterfall" that shows the exact order in which each resource loaded.
Use the Results page and the selected monitor's details page to:
- Select a resource to view load timing, response and request headers, and other details.
- Use these waterfall details to find problems and diagnose performance issues.
- Run rechecks to verify a single failing location or result when needed.
To access a complete list of monitor results from the Results page:
- Go to synthetics.newrelic.com > (select a monitor) > Results.
- To find the type of result you're looking for, sort the list and filter by location. For example, to locate an unusually fast response time from Ireland, sort by Duration (asc) and disable all locations except Ireland, EU.
- To understand how your website performed at a specific moment in time, including details of load time and response size, use the Results page's detail view.
|If you want to...||Do this...|
|Get details about page resources||
Use the timeline view. (For ping and API test monitors, there may be only one page resource.)
From the timeline view, you can:
|View transaction traces||
Selecting a transaction trace will also reveal more details in New Relic APM.
|Verify a single failing location or result||
Select the monitor, then click Recheck.
|Share a result||
Copy the unique URL from your browser's address bar; for example:
You can then share this URL with anyone else who has access to your New Relic account data.
|Quickly access another monitor||
View script logs
Scripted browser and API test results also include a Script log, which includes the contents of the selected script. You can also manually record script milestones by including logging functions in your script.
The console log is located at the end of the script log:
// ----------------------------------- Console log Loading website New Relic Docs Verifying the title Documentation | New Relic Documentation Verifying an element exists tag name h1 If we got this far: SUCCESS!
For some monitor types, the overall monitor check duration will be larger than the individual page request durations. This is because some browser behaviors are not measured individually but still count towards the total check time.
Examples of unmeasured behaviors include:
- Resource pre-fetching and prioritization
- DNS pre-resolve
- TCP pre-connect
- Page pre-rendering