Synthetic Classic has reached end of support and is no longer available. Existing Synthetic Classic customers have been upgraded to the all-in-one Dynatrace software intelligence platform.

Private Last Mile test settings

Settings for a Private Last Mile test consist of:

Note that:

  • When adding a test or when provisioning a test template, only the basic settings are available.
  • When editing a single Private Last Mile test, all settings are available.
  • When editing more than one test, the Basic Settings and Advanced Settings tabs are merged to create the Common Settings tab. This tab lists the tests you selected for editing and the Private Last Mile settings that you can edit.
  • Private Last Mile tests have a fixed frequency of an hour. You can configure the test to run once or multiple times per hour, but you can't schedule the test to run once every two hours or longer than that.

Basic Settings

Test List

If you selected to edit more than one test, the Test List section at the top of the page lists each test you selected to edit and its status.

To remove a test from editing, click . For more information about editing multiple tests, see Editing Performance tests.

Edit Test name

If you selected a single test to edit, the Edit Test Name field displays its name.

This setting is not available when creating a test template.

To rename a test, use these valid characters:

  • Letters
  • Numbers
  • Spaces
  • Period ( . )
  • Forward slash ( / )
  • Colon ( : )
  • Underscore ( _ )
  • Equal sign ( = )
  • Comma ( , )

The name cannot include the following reserved terms:

  • delete
  • drop
  • exec
  • insert
  • update

This setting is not available when creating a provisioning template.

Specify Test URL

This setting appears for tests provisioned with URLs and for Web Recorder transactions. It shows the initial URL for the test. You can change the URL when editing the test, but be aware that the change may impact subsequent test actions.

This setting is not available when creating a provisioning template.

Select Test Status

The test status can be:

  • Active – Currently collecting data based on the test configuration settings and is available for charting, reporting, and trending.
  • Inactive – Currently not collecting data and is available for charting only.
  • Delete – Remove the test from the Portal and the database. The test is not available for charting, reporting or trending. This option is not available when first adding a test.

This setting is not available when creating a provisioning template.

Peer Populations and IP Preference

IP Preference

The IP Preference selection determines the populations that appear in the list:

  • IPv4/IPv6 Mixed – Use IPv6 if it is available, otherwise use IPv4.
  • IPv6 only
  • IPv4 only

When configuring a new transaction, the default value is one of these, in order, depending on whether a preference has been specified:

  1. Script preference setting
  2. Account preference
  3. IPv4/IPv6 Mixed

If you are adding multiple scripts and these scripts were configured in the Windows Recorder with different IP preferences, the lower common preference is the default. The higher preference is IPv4, and the lower is IPv4/IPv6 Mixed. For example, if you add two scripts, one configured as IPv4 only and the other as IPv4/IPv6 Mixed, the default value shown is IPv4/IPv6 Mixed.

Peer Populations

  1. Select the Peer Populations to be used for this test.

    All default and custom Peer Populations appear in the list.

    Use the search field to enter criteria to locate the populations. Populations matching the search criteria appear in the list as the criteria is entered or change.

    To view all populations again, clear the search field.

  2. Specify the number of measurements per hour to be used for this Peer Population in the measurements per hour field prior to moving it.

    • Choose the population and click or double-click a population to move it.
    • Select multiple adjacent populations by holding the Shift key and using the mouse to select the first and last population.
    • Select multiple discrete populations by holding the Ctrl key and selecting the populations.

As Peer Populations are added, the fill rate probability and the number of measurements for that Peer Population is shown. Continue adding populations until there are no more measurements to allocate.

Fill Rate Probability

The Fill Rate Probability indicates the likelihood that the number of you selected can be achieved by the selected Peer Population. Click here for more information.

Include Objects

A page object is a single downloaded file, such as HTML, a GIF image, a Java application, or a Shockwave file. This setting determines if object- and component-level data is stored.

All Page Objects

If All Page Objects is selected, data is collected on each object on the page and object- and component-level data is stored for 45 days.

Selecting this option enables you to drill down to times for individual objects.

No Page Objects

Use this option to chart the flow of the steps in the transaction, but not the individual objects. If you are simply testing the availability of a site, you may not need the object load detail.

If No Page Objects is selected, the objects are downloaded with the transaction, but no detailed component- or object-level data is stored. You can chart the response time for the page, but the drill down to the individual objects on the page is not available. If object errors occur, the errors will not be reported in the Portal, and alerts will not be triggered.

Note that if No Page Objects is selected, the Screen Capture on Error (SCoE) setting is not available.


Select from these options.

Client (non-network) time in results

Client (non-network) time, also called render time, refers to the time spent by the client browser rendering the page, rather than the time spent downloading objects for the page.

When a page is being displayed in the browser, there is processing time by the browser after the objects are downloaded. That non-network time is not displayed in a waterfall chart by default; however, you can enable the reporting of client rendering time in the charts.

  • If the option to include client (non-network) time is disabled, the objects are displayed in the waterfall chart one right after another.

  • If client (non-network) time is enabled, gaps appear while the rendering takes place before the next page download begins.

    When you select this option, the waterfall chart displays W3C metrics.

Enable SPDY Support

Select whether to enable SPDY support. This option is not available for Internet Explorer Browser Agent tests.

SPDY is a networking protocol for transporting web content and is designed to reduce the latency of web pages.

Set Trace Route

If errors are detected, Trace Route records the route the data travels between hosts. This information can help identify which node on the network may be causing a slow response.

This option is Off by default. Select Trace Route on Error to collect trace route information.

Screen Capture on Error (SCoE)

Use the Screen Capture on Error (SCoE) setting to capture transaction information when an availability error occurs at the time the test is executed. The information that can be captured includes page shots, route tracing, and HTTP header information. For details, see Viewing Screen Captures.

Note that a fixed number of tests per account can be configured for SCoE.

This option is not available if you selected No Page Objects.

Set Test Expiration Date

Select the expiration date for the test.

  • Expires on – Click the calendar icon to select an expiration date from the calendar.
  • Expires in – Enter the number of days the test will run, up to a maximum of 15 days.

The Portal automatically deactivates any test that reaches its expiration date at 0:00:00 GMT on the specified date.

Before the test expires, an email is sent to notify the contact person for the account of the pending test expiration.

If you need to find out who the contact person is for your account, or to change the contact person, open a Support ticket. You will need to provide your account name and account ID, which are displayed on the Account settings page.

This setting is not available when creating a provisioning template.

Save Test To

Use this setting to assign a test to a folder.

Use folders to organize tests if you have multiple tests running in your account. For example, if you have multiple tests for a website's workflow, you can group all these tests into a folder, and use the folder to create a Status overview tile in a custom dashboard to monitor the tests as a unit.

The folder options are:

  • Keep the default of <No Folder>.
  • Click <No Folder> and select an existing folder from the list.
  • Create a new folder: Select New folder and enter the folder name in the field.

Valid characters for a folder name include:

  • Letters
  • Numbers
  • Spaces
  • Period ( . )
  • Forward slash ( / )
  • Colon ( : )
  • Underscore ( _ )
  • Equal sign ( = )
  • Comma ( , )

The name cannot include the following reserved terms:

  • delete
  • drop
  • exec
  • insert
  • update

You can use the Folder management page to create folders and manage their contents.

Advanced Settings

The Advanced Settings are available after you provision a test, when you open the test for editing. These settings are not available when you're creating a provisioning template.


Transaction Steps

Use transaction steps to rename steps so that they are more descriptive. For example, rename a step "Home Page" instead of the URL for the page.

Parameters: Defaults

Use parameters to change script values without having to edit the script. This is a useful setting for values that change periodically, such as a password.

If parameters are defined in the transaction (recorded in the Web Recorder or the Windows Recorder), this section lists the default values. If needed, enter a new value for each parameter.

If no parameters are defined for the test, the message "There is no default parameter value" appears.

Optional Data Collection

Select either or both of the following options:

  • Request/Response Header Capture – Enable to capture request/response header information.

    The option to capture request/response header information is not available if you selected the No Page Objects option for page object collection.

  • DNS Server Used – Enable to collect data regarding the DNS servers used by the client for this test.

HTTP Version

Select the header setting to be used when the test runs. The options are HTTP 1.0 or 1.1.

Additional HTTP Headers

Use this section to specify additional header information such as cookies, cache control, GZIP encoding control, or connection keep alive rules.

Maintenance Windows

Use this setting to define a test-level maintenance window. Administrators can also set account-level maintenance windows.

Set a recurring or one-time maintenance window by clicking Add Window.

To delete a maintenance window, select in the row of the window to delete.

Tests can also be added to or removed from maintenance windows in the Maintenance windows page. To go to this page, select Menu icon > Maintenance window.

Recurring Maintenance Windows

Use recurring maintenance windows to define time periods during which testing will temporarily be stopped.

By default, this is populated by any maintenance windows listed in the Test defaults page.

Select the day, start time, and end time for the new window.

One-Time Maintenance Windows

Set a single, specific time, during which time testing will be temporarily stopped.

The one-time maintenance window begins at an explicit start date and ends at an explicit end date. After this defined date range, the one-time maintenance window will have no further behavior.

Select the day, start time, and end time for the new window.