The Result Details view contains information about check results in a number of charts, graphs and tables. This view is most useful for analyzing browser results for scenarios. The type of information displayed in the view depends on the check type. For a scenario, several aspects of the check are shown in different areas. For example, a Scenario Check could have several areas dealing with different aspects of the scenario:

Depending on the type of check, different areas may be available in the view.

Access & Bookmarks

In most cases you can access the Details view by clicking a check wherever it is presented. Depending on the view you are in, the exact method to access the details varies. Whenever you access check Check Details, a bookmark is placed at the top of the window. The results bookmark shows the check url / name:

A similar bookmark is created for Result Details. The results bookmark shows the timestamp:

This allows you to keep a number of checks in the bookmarks bar and move between them by clicking the respective bookmark.

Clicking a bookmark will take you to the appropriate Check Details or Result Details detail view.

Domains

The Domains section displays a table containing the domains accessed in the check. For each, aggregated information about traffic volumes and percentages is shown.

Timeline

In order to view the legend for the timeline, point the cursor at the domain url in the table.

A tooltip with the legend is displayed.

Domains Legend

The Domains Legend window is displayed when you point at a domain url.

It shows explanations for the colors used in the diagram. It also shows the actual time for each of the categories.

Elapsed Time

The Elapsed Time Per Page section shows the distribution of response times for the pages in a scenario .

View

Errors

The Errors section displays errors encountered during the scenario run for the check, if any. For each page that has errors, a table is shown which contains information about the errors.

Jump To URL

The Jump To URL link lets you navigate to the URL in the Waterfall where the error occurred.

Request

The Open link in the Request column allows you to try to send the request manually.

URL

When you click a particular URL in the table, detailed information about the response is shown.

Error Types

There are a number of error types that can be reported for a step.

Job Timeout

• A job timeout error means that the scenario step running time has exceeded the allowed time.

• Causes

  • The job timeout error can mean that a single scenario step runs for too long, due to a coding problem, or some other reason.

  • There can also be connection issues or very slow - or none at all - responses from the target server.

• The default job timeout is 180 seconds.

Redirect Loop

• The Redirect Loop error typically indicates that the there isa circular redirection happening with the request.

• Causes

  • The typical cause of this error is a page that redirects to another page which in turn (possibly via multiple other pages) redirects back to the original page.

  • Redirect loop errors can also occur when the page redirects to itself, possibly due to a programming error or misconfiguration of an htaccess file or the web server.

  • Additionally, and more rarely, the error can be trigged if there is no actual loop, but there are too many HTTP redirects before a page is reached that does not also issue a redirect.

Page Timeout

• A Page Timeout error happens when the total load time for a single page exceeds the threshold value.

• Causes

  • The page timeout happens after a page has started loading, but no new events are received, and no other page has started loading.

  • The timeout occurs if a DOM has not been received (page timeout while waiting for DOM Complete event).

  • It can also occur if there is at least one response missing for one of the sent HTTP requests (page timeout while waiting for resources).

  • This means that the page is reachable, but for some reason takes a very long time to load, and there is no transfer to a different page.

• The default threshold value is 80 seconds.

• Changing the value

  • The Page Timeout value can be changed from the check configuration. Changing the URL Timeout will affect the Page Timeout value. The URL Timeout value is added to 40 to generate a new Page Timeout value.

URL Timeout

• The URL Timeout error is triggered whenever the response time for a single URL request exceeds the threshold value.

• Causes

  • Url timeout is setup separately for every URL to track debugger notifications it receives. If no events are received for a URL in urlTimeout seconds then it will be reported as timed out.

• Setting

  • The default threshold value is 40 seconds. This can be configured in the advanced section of the check configuration.

• Changing the value

  • Changing the URL Timeout (Error Types) will affect the Errors Types Page Timeout value. The URL Timeout value is added to 40 to generate a new Page Timeout value.

History Information

The History Information table shows information about the check run.

This information is available if the full browser result information is not relevant for the check type or has been purged.

Legend

The Legend section shows explanations for the colors used in a diagram. The legend varies slightly depending on which graph or table it relates to. For example, the legend for page information:

Domains Legend

The Domains Legend window is displayed when you point at a domain url.

It shows explanations for the colors used in the diagram. It also shows the actual time for each of the categories.

Slowest URL Legend

The Slowest URL Legend window is displayed when you point at a url in the table.

Shows explanations for the colors used in the diagram. It also shows the actual time for each of the categories.

Waterfall Legend

The Waterfall Legend section shows explanations for the colors used in the waterfall diagram.

View

DOM Content Loaded

The DOM Content Loaded point is when the render tree can be constructed: the DOM is ready and there are no stylesheets blocking JavaScript execution.

This measure calculates duration between the EventStart and EventEnd timestamps, to allow for JavaScript frameworks waiting DOM Content Loaded before starting execution.

DOM Complete

The DOM Complete point is when the resource loading and processing is complete.

Scenario

The Scenario Details section shows information about the scenario used in the check.

Masking Values

When command values contain sensitive information, they can be masked. This will prevent the value from being displayed in results.

Example

Let’s assume you use a scenario with the following commands:

\{\{${maskapicaPassword}\}\}

If you want to mask the value secretPa$$word in the Check Result page the following steps are required:

• Add the command Store to store the password as a variable with the prefix maskapica

• Use this variable with the actual command which uses the password.

Your commands should now look like this:

\{\{${maskapicaPassword}\}\}

When Synthetic Monitoring runs a check using this scenario the result will be saved with the executed scenario commands list as the example above. When Synthetic Monitoring shows the check result on the check results page Synthetic Monitoring will recognize that there is a command value which starts with maskapica.

The command’s target will be masked on the the check results page:

\{\{${maskapicaPassword}\}\}