---
title: View simple and scripted monitor results
source: https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/view-simple-scripted-monitor-results
---

Synthetic monitoring automatically records each simple and scripted browser monitor check, allowing you to see the load time and response size for every run, as well as 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 details to find problems and diagnose performance issues.
-   Run [rechecks](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/recheck-failed-monitors) to verify a single failing location or result when needed.

> #### 💡 TIP
>
> For information on ping monitors, see [View ping monitor results](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/view-ping-monitor-results).

## View results [#finding]

To access a complete list of simple and scripted monitor results from the [**Results** page](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/pages/synthetics-results-access-individual-monitor-runs):

1.  Go to **[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** > (select a monitor) > **Results**.
2.  To find the type of result you're looking for, [sort the list](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/pages/synthetics-results-access-individual-monitor-runs#sort-list) and [filter by location](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/pages/synthetics-results-access-individual-monitor-runs#filter-location). For example, to locate an unusually fast response time from Ireland, sort by **Duration (asc)** and disable all locations except **Ireland, EU**.
3.  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.

![Synthetic monitoring - Results page](https://docs.newrelic.com/images/synthetic_screenshot-crop_ResultsPage.webp "Synthetic monitoring - Results page")

**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** > (select a monitor) > **Results** > (select a result: View details of each monitor check, including load time and total load size.

You can also access interesting results for your simple and scripted monitors directly from the [**Overview**](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/pages/synthetics-overview-page-view-monitors-performance) and [**Failures**](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/pages/synthetics-failures-troubleshoot-downtime) pages.

| **If you want to...**                      | **Do this...**                                                                                                                                                                                                                                                                                                                                                                |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Get details about page resources           | Use the timeline view. (For API test monitors, there may be only one page resource.) From the timeline view, you can: - See the exact order in which each page's resources loaded. - See how long each element took to load. - Select a resource to view detailed metrics, including HTTP status codes, [timing information](#timing), response headers, and request headers. |
| Verify a single failing location or result | Select the monitor, then click [**Run check**](https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/using-monitors/recheck-failed-monitors).                                                                                                                                                                                                                        |

## View script logs [#viewing-logs]

Scripted browser and API tests often generate script logs, which provide valuable insights into how your script executes. These logs include the contents of the selected script along with any custom logging messages you've added.

Here's how to view script logs:

1.  Navigate to **Synthetic Monitoring > Results**.
2.  Select a specific test result.
3.  Click on the **Script Log** tab.

> #### 💡 TIP
>
> Script logs are only available for tests that have failed or where the user has opted to include custom logging.

If you want to manually record script milestones, you can [include logging functions in your script](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/scripting-monitors/introduction-scripted-browser-monitors/#script-log-manual).

## View monitor screenshots

Simple browser and scripted browser monitors can take screenshots. By default, both simple browser and scripted browser monitors take screenshots only if a check fails. However, scripted browser monitors can take a screenshot on every check if you manually call [take screenshot](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/scripting-monitors/synthetic-scripted-browser-reference-monitor-versions-chrome-100#webDriver-takeScreenshot) in your script.

> #### 💡 TIP
>
> Keep in mind that scripted browser monitors only save the last screenshot taken.

![Synthetics-View-Screenshot.png](https://docs.newrelic.com/images/synthetic_screenshot-crop_results-fail-page.webp "Synthetics-View-Screenshot.png")

**[one.newrelic.com > Synthetic monitoring](https://one.newrelic.com/synthetics-nerdlets)** > (select a monitor) > **Results** > (select a result).

## Timing details [#timing]

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:

-   JavaScript interactions
-   Resource prefetching and prioritization
-   DNS pre-resolve
-   TCP pre-connect
-   Page pre-rendering
