Skip to main content

View 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 Run History 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.
  • Rerun monitors to verify a single failing location or result when needed.

View results​

To access a complete list of simple and scripted monitor results from the Run History page:

  1. Go to console.boltic.io > Monitor > (select a monitor) > Run History.

  2. To find the type of result you're looking for filter by location. For example, to locate an unusually fast response time from Tokyo, filter by and disable all locations except Tokyo, JP.

  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.

    Results Page

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, response headers, and request headers.

Verify a single failing location or result

Select the monitor, then click Run check.

View script 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 Monitor > (select a monnitor) > Run History.

  2. Select a specific test result.

  3. Click on the Script Logs tab.

    Script Logs
Important

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.

Timing details​

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