Configure browser monitors

Dynatrace allows you to configure your browser monitors easily when first setting them up and at any time thereafter.

During browser monitor creation (single-URL or clickpath), configuration settings appear after you select Create a browser monitor. These settings are a subset of the full set available in edit mode (described below) after the monitor has been deployed. For example, you can set performance or availability thresholds only after monitor creation.

Configure an existing browser monitor

To configure/edit an existing single-URL browser monitor or browser clickpath

  1. Go to Synthetic in the Dynatrace menu.

  2. Select the browser monitor you want to configure.

  3. Select the Browse button () > Edit. Alternatively, you can go to the Synthetic monitors page, select the check box next to the monitor you want to edit, and select Edit at the bottom of the page.

  4. Browse through the Monitor settings tabs on the left to configure settings (see explanations below—a subset of these settings are available when you first set up a monitor).

  5. Save changes at bottom right when done editing your monitor. (You can also Discard changes.)

Monitor setup

Specify the Monitor name. The name is limited to 500 characters.

For single-URL browser monitors, you can edit the HTTP/HTTPS URL of your monitor here. (For clickpaths, this information is captured in the Navigate event.)

Define device emulation settings

Emulated device properties are the Device profile/type, orientation, Screen size, Bandwidth, and User agent.

The default device profile is Desktop.

  • For mobile device profiles (including tablets), you can select an orientation and Bandwidth. The User agent is auto-selected but can be changed.
  • For a Custom device, specify if the device is a Mobile device and select the orientation, Bandwidth, and Screen size. This profile uses the default Dynatrace user agent, which can be changed.
  • For desktop and laptop profiles, you can choose Bandwidth. These profiles use the default Dynatrace user agent.

Select a key performance metric for this monitor

This setting is available in edit mode only.

You can choose one key performance metric for each load action and XHR action included in a browser monitor or clickpath.

Key performance metrics enable you to choose performance goals that best fit the variable needs of each application you monitor. For example, you might want to choose User action duration to optimize the performance of a traditional web application. For other applications where the speed of user interaction is more important than the UI, you might want to optimize the time it takes for JavaScript resources to load. The default is Visually complete for both load and XHR actions as it measures how long it takes for the visible portion of a user’s browser to be fully rendered.

As Dynatrace captures a list of key performance metrics out of the box, you can switch your selection in monitor settings and immediately have historical data available.

Monitor settings KPM

The key performance metric is calculated and displayed as an average in the Synthetic details page in the performance visualizations and in the Synthetic events and actions card.

Assign synthetic monitor to a web application

This setting is available in edit mode only.

If this synthetic monitor is associated with one of your monitored applications, you can assign the monitor to the application so you can track application availability and performance. Detected problems are then automatically associated with your application. If the monitor is unavailable, the associated application is also considered to be unavailable.

Select Assign monitor to application and choose an application from the list. You can assign a monitor to multiple applications, and an application can have several assigned monitors. Select Connect another application to add an additional application.

Recorded clickpath

You can edit a recorded clickpath.

When your recorded clickpath captures a credential such as a password, you are notified and given the option to save it to the credential vault. The image below shows a recorded clickpath with a captured password.

Captured credential

Read more about credentials in the Navigate event and Keystroke event.

Select Record again to re-record your clickpath. Note that any JavaScript events that precede an initial Navigate event will be erased when you re-record your clickpath—see Browser clickpath events. You can also perform local playback (Play back clickpath) so you can verify that your recorded clickpath plays back as expected.

If your browser monitor has any associated credentials, whether public or owner only, users need to enter the credentials in order to play back the monitor locally. However, if you Enable local playback of Synthetic browser monitors without entering credentials in the credential vault, users need not enter the credentials that they have access to in order to play back the browser monitor.

For example, if you want to play back a clickpath containing one public credential and one owner-only credential belonging to another user, you don't need to enter the public credential. In effect, this means that you might not be able to play back a clickpath containing credentials to which you don't have access.

Play back clickpath

You can opt to keep the playback window open after playing back a clickpath (Keep window open after playback), say, to debug a failed execution or test some JavaScript code on the website.


  • Each monitor run begins in a clean state, that is, with a clean browser cache and empty local storage.
  • Local playback in Dynatrace is in emulation mode, based on the device profile and user agent you select during monitor configuration. That is, playback emulates your chosen device. If you navigate to the same URL or perform the same transaction outside Dynatrace, your experience might vary.

You aren't limited to just one mode to view and edit your clickpath—you can switch back and forth between the UI and script modes by selecting Clickpath or Script. For details on editing your clickpath in JSON format, see Script mode for browser monitor configuration.

In visual/UI mode, you can avail of these controls to edit events in your script:

If necessary, you can delete events from your clickpath by selecting x under Delete for the respective event. You can also add events—select Add synthetic event. Specify a name, event type, and the event it should follow.

Use the Move up/down arrows Reorder events to reorder events. Note that the first Navigate event of a clickpath can be preceded only by JavaScript events.

Although we do our best to name events intuitively, you can edit event names as required—simply click in the field provided for the event name.

In addition, you can configure each individual event by hovering over it and clicking when your cursor changes to a finger pointer. From event details, you can delete the event by selecting Delete synthetic event. Note that the first Navigate event of a clickpath cannot be deleted.

The fields available to edit depend on the event type—see Browser clickpath events for detailed descriptions. When you are done editing, be sure to Save changes. Select Close details to exit event details if necessary.

Synthetic event UI


A clickpath event is not the same thing as an action. See Number of actions consumed by browser clickpaths for details.

Frequency and locations

There are two factors that make up your monitoring schedule—how frequently your browser monitor runs and the number of locations it's executed from.

Dynatrace offers a global network of public Synthetic Monitoring locations out of the box. Note that you can also create private Synthetic locations within your own network infrastructure. Both public and private locations appear on this settings page.

The frequency and number of locations determine the number of monitor executions per hour. For example, running a monitor from 3 locations every 15 minutes results in 12 executions per hour. Browser monitors are evenly spaced, running at 5-minute intervals.

You can choose a frequency of every 5, 10, 15, or 30 minutes; or 1, 2, or 4 hours. You can also select multiple global locations from where your browser monitor is to be executed.

Note that all public Synthetic locations are set to Coordinated Universal Time, or UTC. If your monitor script requires the local time or time zone, you can use the api.getContext() method and the system clock to implement conditional logic.

Validate content

For single-URL browser monitors, this tab appears in Monitor settings and is only available in edit mode.


For browser clickpaths, you can set up content validation per event in the Recorded clickpath tab of Monitor settings. You can also set up validation to recorded or manually inserted clickpath events during the recording workflow.

Content validation helps to verify that your browser monitor loads the expected page content or element. Validations are performed through validation rules—select Add custom content validation to define a validation rule.

In browser clickpaths, you define validations for each event; for single-URL monitors, you define validation for the monitor as a whole as they only contain a single event.

All validation is performed after following all redirects, even if the very first response delivers HTML content.

You can validate based on specific text on a web page, a specific element, text included within an element, or text in the DOM or any resource. You can opt to pass or fail your monitor/event based on your validation criteria. If pass criteria are not met (or fail criteria are met), the monitor/event fails and the execution is aborted.

Validation criteria

When defining validation, specify the tab (Target window) in which the text/element should be found.

If your validation is based on content (contains text), the markup text for an element (contains text in element), or text in the DOM or a resource (contains text in DOM or any resource), you must provide the text string (Specify text). Enclose placeholder values in brackets, for example {email}. Optionally, you can specify text as a regular expression (Evaluate as regular expression).

If your validation searches for an element (contains element) or the markup text for an element (contains text in element), you must specify the CSS Selector or DOM locators to use during replay—select Add locator, then select DOM or CSS, and provide the locator reference. You can add as many locators as you like.


You can add more than one validation to an event/monitor. If you have defined multiple validation rules, you can reorder and delete rules as required.

Validation rules

You can play back your single-URL browser monitor from here (Play back monitor). Read more about local playback above.

Outage handling

This setting is available in edit mode only. These options determine what to do in the event of availability outages.

You can disable problem generation for global and local outages if you're testing a volatile site or have scheduled downtime that you don't want to be alerted on.

  • Generate a problem and send an alert when this monitor is unavailable at all configured locations

    This setting is enabled by default for newly created monitors. It alerts you of global availability outages, that is, when all locations experience a failure simultaneously.

  • Generate a problem and send an alert when this monitor is unavailable for one or more consecutive runs at any location

    This allows you to raise a problem when there are consecutive failures at one or more locations.

    In the example below, a monitor is configured for 4 locations, and a problem will be generated if 3 of those 4 locations are unable to access your site during 2 or more consecutive runs.

  • Ignore specific status codes

    This enables you to exclude HTTP status codes 400–599 from causing availability outages/errors if encountered in the main document request. Typically, this is the base page in a load action. With this setting enabled, if the base page of a load action encounters HTTP errors 400–599, an availability outage will not be triggered.

    You can specify an exact status code, range, or status class mask. Use commas to separate multiple values; use the minus sign (-) with no spaces for a range, for example, 404, 405-410, 5xx. You can opt to apply the rule only to document requests matching a specific regular expression (Only apply to document request matching this regex).


    • This setting does not apply to XHR requests or document requests in iframes; browser monitors do not fail when an XHR request or a document request in an iframe fails.
    • This setting applies to future executions, that is, executions that take place after the setting has been enabled.
  • Automatic retry on error

    With this setting, enabled by default, single-URL browser monitors and browser clickpaths are automatically retried from the same location when errors are encountered. Upon subsequent success, the initial error data point is discarded. This approach reduces false positive errors.

    Retry on error occurs regardless of your availability thresholds. The retry does not consume additional DEM units.

    You might want to disable retries when investigating underlying issues if retries might mask the issues. With retries disabled, every monitor failure counts towards an outage.

Outage settings browser monitors

An outage problem is resolved when there are as many consecutive successful executions as the configured number of failed executions for generating the problem. The successful executions must occur on the number of locations that = the total number of locations–number of locations required for the problem+1.

Note that when a global outage problem is resolved, you might still have one or more locations experiencing monitor failure. Set up local outage rules to be alerted on these.

See Synthetic calculations for more information on:

Performance thresholds

This setting is available in edit mode only.

Performance thresholds enable you to be proactive about site latency.

Select Add threshold. For clickpaths, you can set a threshold for the monitor as a whole (Total duration of all events) and/or individual events. Note that you can only select events that generate network activity. In the case of single-URL browser monitors, you can only set a threshold for the monitor as a whole.

Select an action for performance thresholds

You can see the 24-hour average performance up until that point to help you set a threshold. Simply enter a performance Threshold in seconds and Save. You can set multiple performance thresholds.

Set a performance threshold

You can delete or edit your performance thresholds at any time.

Performance thresholds are defined as the Total duration of the monitor or of individual events, which, in turn, can comprise multiple load or XHR actions.

Note that Total duration is not available as a metric for individual load or XHR actions when viewing browser monitor Multidimensional analysis or a waterfall graph.

Performance thresholds

Dynatrace generates a performance problem if a monitor at a given location violates any of the defined performance thresholds in 3 of the 5 most recent executions, unless there is an open maintenance window for the monitor. That is, the violations must occur at the same location. Multiple locations can have such violations and be included in a problem.

The problem is closed if the performance thresholds are not violated in the 5 most recent executions at each of the previously affected locations.

See Synthetic calculations for more information.

Monitor script

This tab appears for single-URL browser monitors and contains the script code of the monitor in JSON format. You can edit the script directly in the Dynatrace Portal or Download the script to edit in a text editor of your choice. For details, see Script mode for browser monitor configuration.

Advanced setup

This tab contains controls for:

During the creation of single-URL browser monitors or clickpaths, these controls are listed as Additional options for monitor configuration.

Enable global login authentication


This setting is available for single-URL browser monitors.

For browser clickpaths, login automation does not appear within Advanced setup. Basic authentication for clickpaths is included in the Navigate event. For HTML-based (web form) authentication, you can capture entering the username and password for used authentication in your recorded clickpath (see Supported authentication methods in Synthetic Monitoring)

Dynatrace makes it easy to automate signing in to password-protected pages. This is achieved with Dynatrace LoginSenseTM technology, which enables intelligent and secure login to your web application each time a browser monitor runs.

Enable global login authentication to automate signing in. If your web application requires authentication either via HTTP authentication scheme or a web form, select Basic authentication or Web form, respectively.

Dynatrace stores and manages all Synthetic Monitoring credentials in a credential vault. Credentials are access controlled and can be designated as owner only or public.

You can choose an existing credential (Select credentials). You can only see the credentials that you have access to in this list, that is, public credentials or owner-only credentials created by you.

Login authentication

You can Create new credentials by entering a Username and Password. Provide a name for the credential and Save to vault. The credentials you create this way are automatically set to owner-only permissions and can only be used by you.

Note that you must have permission to access the credential vault in order to create credentials in script or UI mode in a browser monitor in this way. You can always capture entered credentials as part of a recorded clickpath.

Create new credentials

Enable additional HTTP headers

The monitor is created with a bare minimum set of headers required by the protocol. To enable custom headers:

  1. Select Enable additional HTTP headers.
  2. Enter a Header name and Value.
  3. Select Add another header as needed.

You can specify multiple HTTP headers. They will be set for all requests the monitor makes.

If you want to set headers only for specific requests, check Only apply headers to requests matching a pattern and then define a Pattern. After that, the header is only set for requests that match the pattern you’ve defined.

Block specific requests

You can block one or more requests by specifying complete URLs or match patterns. Blocking requests allows you to analyze how these requests affect your application's performance and optimize it accordingly.

Enable Block specific requests. You can then provide a complete URL as shown below.

Block requests

You can also define patterns, for example, *://*/*.png to block all requests to PNG images.

Matching requests are blocked throughout monitor execution and aren’t dependent on events.

Set cookies

Cookies enable you to store browser state information on the client side so that each monitor execution is based on the same state and you can accurately monitor a performance baseline.

You can set cookies in Additional options when creating a browser monitor or in Advanced setup in monitor settings in edit mode. These cookies are valid for the entire monitor execution. If you want to set cookies only for a specific portion of your clickpath, use the Cookie event.

In edit mode, enable Set cookies, then provide a Name and cookie Value. Every cookie must be unique within the list.

The following symbols are not allowed in the cookie value: ;,\". Provide the Domain of the cookie, and optionally, the Path to the cookie. Save your cookie.

Select Add cookie to define additional cookies.

Bypass Content Security Policy (CSP) of monitored page

If you have a Content Security Policy in place, it's likely to prevent the browser from sending monitoring data to the Dynatrace Server. As a first and preferred method to have Chrome bypass the CSP of any monitored pages in your single-URL browser monitor or browser clickpath, enable this option.

Only if you're unable to use this option for some reason, refer to the alternative solutions for bypassing CSP in Browser monitor issues with Content Security Policy.

Capture performance metrics for pages loaded in frames

Enable this switch to begin capturing performance data for pages in iframes or framesets. The resulting waterfall graph for the action in question will contain results for each frame. You can select the page you want to view waterfall data for.


Dynatrace Synthetic Monitoring enables you to capture your metric customizations (filters and splitting factors) as calculated metrics and track their performance over a long term. This tab displays all calculated metrics for your monitor and a count of calculated metrics for your monitoring environment as a whole. The settings in this tab are available in edit mode only.

Expand a metric to view details. You can disable/enable, delete, or create custom charts and alerts based on a calculated metric. While you cannot change metric name, key, or configuration once created, you can choose whether you want to display any splitting factors in custom charts based on the metric.

Metrics tab