Dynatrace allows you to easily configure your browser monitors when first setting them up and at any time thereafter.
During browser monitor creation (single-URL or clickpath), configuration settings appear after you have clicked 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.
To configure an existing single-URL browser monitor or browser clickpath:
- Select Synthetic from the navigation menu.
- Select the browser monitor you want to configure.
- Click the Browse (...) button and select Edit.
- Click through the Monitor settings tabs in the left menu to configure the available settings (explanations below—a subset of these settings are available when you first set up a monitor).
- Click Save changes at bottom right when done editing your monitor.
You can specify the general properties of your browser monitor (for example, Monitor name) as well as the profile of the emulated device (Device type, Bandwidth, and Screen size).
- For mobile device profiles, you can select an orientation.
- For a Custom device, you can specify if it is a mobile device and choose orientation, Bandwidth, and Screen size. The User agent is auto-selected.
Dynatrace makes it easy to automate the login process for password-protected pages. This is achieved with Dynatrace LoginSense TM technology, which enables intelligent and secure login to your web application each time a browser monitor runs.
Use the Automate login feature (disabled by default) to automate logging in. If your web application requires authentication either via a web form or an HTTP authentication scheme, select Web form or Basic authentication respectively and enter credentials.
For browser clickpaths, Automate login doesn't appear within Monitor setup. To find out how to automate form-based login for browser clickpaths, see Basic authentication below.
Assign synthetic monitor to a web application
If this synthetic monitor is associated with one of your monitored web 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 monitor status is unavailable, the associated application is also considered unavailable.
Click Assign monitor to application and select an application from the drop-down list. You can assign a monitor to multiple applications, and an application can have several assigned monitors.
Frequency and locations
There are two factors that make up your monitoring schedule—how frequently your browser monitor runs and which locations it is executed from. The frequency and number of locations determine the number of runs each 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, 30, or 60 minutes. You can also select multiple global locations from where your browser monitor is to be executed.
Content validation helps to verify that your browser monitor loads the expected page content. Content validations are performed through validation rules. Click Add custom content validation to define a validation rule.
In browser clickpaths, you define validations for each action; for single-URL monitors, you define validation for the monitor as a whole as they each contain a single action. You can define as many validation rules for an action as you want.
You can validate that either specific text, a specific element, or text included within an element in the action. You can opt to pass or fail your monitor based on your validation criteria. If pass criteria are not met (or fail criteria are met) the monitor fails and the execution is aborted.
If you choose to validate an element or text within an element, you must additionally specify the CSS and DOM locators to be used during replay.
For browser clickpaths, you can set up validation by selecting Recorded clickpath from the Monitor settings menu on the left. Click an event from the displayed event list to add validation for it.
Browser monitors offer you a few options for alerting you in case of availability outages. With newly created browser monitors, the setting Generate a problem and send an alert when this monitor is unavailable at all configured locations is enabled by default. This setting alerts you of a global availability outage when all locations experience an outage simultaneously.
The Generate a problem and send an alert when this monitor is unavailable for one or more consecutive runs at any location option allows you to raise a problem when there are consecutive failures at one or more locations. In the example below, a problem is generated if 3 of 4 locations are unable to access your site during two or more consecutive runs.
You can also disable both settings. This can be useful if you're testing a volatile site or have scheduled downtime that you don't want to be alerted about.
Performance thresholds enable you to be proactive about site latency. When enabled, simply enter a performance threshold in seconds for single-URL browser monitors. You can see the 24-hour average performance up until that point to help you set a threshold. In the case of browser clickpaths, click Add threshold to set thresholds for the monitor as a whole and/or individual actions.
You can delete or edit your performance thresholds at any time.
If you've recorded a clickpath, you have further configuration options and can edit the clickpath, if necessary.
Select Record again at top right to re-record your clickpath. You can also perform local playback by clicking Play back clickpath so you can verify that your recorded clickpath plays back as expected.
Although we do our best to name actions intuitively, you can edit action names as required—simply click in the field provided for each action name.
If necessary, you can delete unnecessary actions from your clickpath, by clicking x under Delete for the respective action.
In addition, you can configure each individual action by hovering over it and clicking when your cursor changes to a finger pointer.
The fields available to edit depend on the action type.
Amount of time to wait before the next action is triggered
While Dynatrace automatically selects an appropriate wait time for each action, you can customize this setting to define how long Dynatrace should wait before the next action is executed.
Wait for page to load completely waits for network activity to be completed after the load event is triggered. This is the default wait time used when loading a new page.
Wait for background network activity to complete waits for all network activity to be complete following the action. This is the default wait time used for XHR requests and interactions within single-page applications.
This option is not available for Navigate actions.
Wait for specific period of time allows you to specify the number of seconds that Dynatrace should wait between this action and the next.
Wait for specific element to appear allows wait for a specific HTML element on the page by specifying the CSS or DOM locator for the element. You can also specify to text to validate against in the element, and a timeout for locating the element.
Wait for next action waits until one of the locators of the next action is found. This is basically the same as Wait for specific element to appear but automatically uses the locators of the next action.
For browser clickpaths, you can set up content validation in the Recorded clickpath menu of Monitor settings. Click an event from the displayed event list to add validation for it. Validation controls are described in Validate content above.
To automate form-based login, begin by recording your clickpath. During recording, type in your username and password as usual. Your login credentials will be securely recorded and stored so that logging in is automated during monitor runs.
For HTTP authentication, select the Recorded clickpath from the Monitor settings menu after you record your clickpath. Expand the first event of the clickpath, which is always a Navigate event. In the Basic authentication section, type in your username and password.
Edit element locators
When an event in your clickpath targets a specific element on a web page, you can edit the element locators in either DOM or CSS selector format. Locators help the Dynatrace Synthetic Recorder identify the element during playback. Click Add locator to specify a CSS selector or DOM locator. You can also edit or delete any existing locators for your event.