This page covers the basics of using Browser Synthetic Monitoring. You'll learn how to get to the Jobs page, create a job that measures a URL, view the results from the Sessions page, and finally how to edit and delete your job.
Create a Job
- Open one of your browser applications.
- Click Jobs to open the Jobs page.
- If you don't have any previous jobs, click Create a New Job >. If you have previous jobs, click Add.
- From the New Job dialog, do the following:
- For Specify your Test, enter a URL in the URL field and "Example Job" in the Name field.
- For Choose Browsers, select Chrome.
- For Choose Locations, click + and select any location.
- Click Save.
Synthetic Job Locations
For URL measurements and synthetic script jobs, the Synthetic Agent is always run in the configured browser location. The synthetic script, however, is not run on the same machine or location as the configured browser for security reasons. See Synthetic Agent Locations for more details.
View the Results
- From the Jobs page, verify that your job has a check next to it indicating that the job has been enabled.
- After a few minutes, you should see a time that your job was last run and some metrics.
- Select your job and click Details.
- You should now see the results for your job on the Sessions page.
Understand the Results
You can understand the results in several different ways and levels from the Sessions page. You can sort session results by criteria and then examine the details of a specific session in the Session Details. From the Charts tab of the Sessions page, you can then view widgets representing aggregated session data in charts and a configurable set of fields for each session.
The following sections discuss how to use Sessions and Session Details to understand the results of your jobs.
Examine Session Details
You can double-click any session to get a summary of the session, page details, and a breakdown of details for each page in the session. You'll be able to view how the page loaded, the resources that were requested, and the business transaction for each page. You can use this information to find where network latency occurs or where scripts break.
For example, from the Session Details dialog below, you can determine that the visually complete (when the user would see the completely loaded page) took nearly seven seconds and then examine the duration of the page load from the HTTP request to the first byte, from the first byte to DOM ready, and finally from DOM ready to visually complete.
Get a Quick Overview
From the Sessions page, you can click the Charts tab to view widgets representing aggregated session data. For example, the Lowest Availability widget shows you what locations are the least available, so you can confine and focus on issues in specific locations.