Skip to end of metadata
Go to start of metadata

On this page:

Related Pages:

You can configure your jobs in many ways. You can schedule when and how often the jobs run, set timeouts, configure performance thresholds to trigger warning and critical events, and customize connections speeds. Before you configure jobs, first read the instructions in Get Started with Browser Synthetic Monitoring.

The following sections show you how to use the Controller UI to configure your jobs.

Choose Locations

You can choose one or more locations to run tests. The job can be configured to test all of the locations every time or test one location each time the job is run. 

Hosted Agent Locations and Synthetic Private Locations

If you have deployed a Synthetic Private Agent, you will be able to choose Hosted Agent Locations or Private Agent Locations as shown below. The Hosted Agent Locations are where AppDynamics hosts public Synthetic Agents. The Private Agent Locations are where you are hosting your Synthetic Private Agents.

Choose Browsers

You can have the job run the test on one or more different types of browsers. You can also configure the job to run on a mobile browser on one platform, such as iPhone 7 Plus or Pixel. When the job runs tests on mobile browsers, it is actually running the Chrome browser emulator with the profile properties for the specified platform.

All the browsers are running on either Windows 2012 or Windows 2012 R2.

Customize Connection Speeds

You can test the performance of your job based on customized connection speeds. This helps keep job performance consistent and realistic. If you choose Native Connection, the job will run at the maximum speed available to our data centers. The default is Cable (5/1 Mbps 28ms RTT).

Schedule Jobs

When you create or edit your job, you can define the job schedule.


Set Timeouts

You can also set the maximum time for completing a job. The timeout limits the amount of your license consumed by the job. If your job times out, data will still be collected until the timeout expires.

Configure Availability Rules

You can configure your synthetic jobs to check the availability of pages or resources. You do this by setting the session status for when a page fails to load or when a resource is missing or inaccessible. You can also configure the job to ignore when a page fails or a resource is missing/inaccessible.

The screenshot below configures the synthetic job to treat the session as Failed if any page fails to load and treats the session as Warning if any resource fails to load. If the job navigates to a page with an HTTP 4xx or 5xx status code, the session status will be set to FAILED. This, in turn, will trigger a Critical Event that you can set alerts on. If a resource fails to load, the session status will be set to WARNING, which will trigger a Warning Event.

In addition, you can use the Advanced Options to configure the jobs to ignore or only consider certain resources. For example, the advanced options shown below might be used to ignore resources such as fonts, which browsers may not have, and only consider certain types of resources such as images, CSS, JavaScript, etc, that may have a higher impact on your pages.


Favicons are always ignored when checking the availability of resources.

Configure Performance Thresholds

Your job can send warning events based on configured thresholds. If you check either or both of the Automatically retest after warning events or Automatically retest after critical events check boxes, then exceeded thresholds will trigger the execution of the job to be immediately repeated after the event is generated.

For example, if the threshold for critical events is exceeded, the event Critical Started will be triggered and the test rerun. If the same threshold is exceeded for the repeated test, the event Critical Confirmed will be triggered and the test once again rerun. If the threshold continues to be exceeded, the event Critical Continues will be triggered and the test rerun.

From the Events page shown below, you can see that the results of the first and successive tests exceeded the threshold for critical events and triggered the Critical StartedCritical Confirmed, and Critical Continues events.

Also, see Alerts for Browser Synthetic Monitoring for more information.