Dynatrace allows you to easily configure your browser monitors at any time.
To configure an existing browser monitor
- Select Synthetic from the navigation menu.
- Select the browser monitor you want to configure.
- Click the Browse (...) button and select Edit monitor.
- Click through the Monitor settings options on the left-hand menu to configure the available settings (see explanations below).
- Once you've finished configuring your browser monitor, click Done.
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).
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 into your web application each time a browser monitor runs.
With browser monitors you can use the Automate login feature to automate the login process for password-protected pages. The default login option is No login, which means that no login is required. If your web application requires authentication either via a web form or an HTTP authentication scheme, select Web form or Basic authentication respectively and type in your credentials.
In case of browser clickpaths, the Automate login section doesn't appear within Monitor setup. To find out how to automate form-based login in case of browser clickpaths, see Basic authentication below.
Frequency & locations
There are two factors that make up your monitoring schedule, how frequently your browser monitor runs and which locations your browser monitors are executed from. The frequency and number of locations determine how often your browser monitor runs each hour. For example, running from 3 locations every 15 minutes results in 12 browser monitor executions each hour. Browser monitors are evenly spaced, running at 5-minute intervals.
You can choose from 5, 10, and 15, 30 and 60 minute frequencies. You can also select multiple global locations where your browser monitor is to be executed from.
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 an 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 choose the number of locations at which an outage can occur during multiple, consecutive occurrences before a problem is raised. In the example below, a problem will be generated if 3 of 4 locations are unable to access your site during two or more consecutive browser monitor runs.
You also have the option of disabling 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, you can click Add threshold to set a threshold that meets your needs. This setting notifies you when a specific action or browser monitor exceeds the threshold from any single location 3 times consecutively. If your browser monitor includes a clickpath with multiple actions, you can set a performance threshold for one or multiple actions. You can delete or further 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.
Click the Browse (...) button at the top of the monitor page and select Record again to re-record your clickpath. You can also perform local playback to confirm the accuracy of the monitor by clicking the Play back actions button. This feature enables you to verify that your recorded clickpath plays back as expected.
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 expanding the Edit column.
Edit action name
Although we do our best to name actions intuitively, you can edit action names as required.
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 for an action to complete 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.
- Wait for specific period of time allows you to specify the number of seconds that Dynatrace should wait between this action and the next action.
- Wait for specific element to appear allows you to specify a locator to wait for, providing you with the option of waiting for a specific HTML element on the page.
- 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.
Content validations help to verify that your browser monitors load the expected page contents. Content validations are performed through validation rules. Click Add custom content validation to define a validation rule. 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 appears within the action. If the expected content doesn't appear, the clickpath will fail and the execution will be aborted.
If you choose to validate an element or text within element, you have to additionally specify the CSS and DOM elements to be used during replay.
For browser monitors, you can perform content validation by selecting Validate content from the Monitor settings menu on the left.
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 the next time the clickpath runs, the login will be automated.
In case of HTTP authentication, you have to select the Recorded clickpath option from the Monitor settings menu and expand the first action of the clickpath, which is always a Navigate action. In the Basic authentication section type in your username and password.
Edit element locators
You can edit the element locator values to help the Dynatrace Synthetic Recorder identify the CSS and DOM elements you want to use during replay. To specify the CSS and DOM elements, click Add locator.