How do I configure my web checks?

If you're creating a new synthetic monitor, begin by following the steps for creating an availability web check or recording a clickpath web check to access the Configure web check settings page. Then proceed with the steps outlined below.

To configure an existing web check

  1. Select Synthetic availability from the navigation menu.
  2. Select the web check you want to configure.
  3. Click the Browse (...) button and select Edit web check.
  4. Click through the Web check settings tabs to configure the available settings (see explanations below for details).
  5. Once you've finished configuring your web check, click Done.

The available configuration options are briefly explained below.

Web check setup

You can specify the general properties of your web check here (for example, Web check name) as well as the profile of the emulated device (Device type, Bandwidth, and Screen size).

Automated login

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 web check runs.

With availability web checks you can use the Bypass 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 this option (see image below) and type in your credentials.

To automate form-based login for a clickpath web check, 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 web check runs, the login will be automated. In case of HTTP authentication, you have to select the Recorded clickpath option from the Web check settings menu and expand the first action of the clickpath ([see Recorded click path section below]({% link_to_id D4.4%}#recorded-clickpath)), which is always a Navigate action. Click the Advanced action configuration link at the bottom of the action detail section and type in your username and password.

Monitoring schedule

There are two factors that make up your monitoring schedule, how frequently your web check runs and what locations your web checks are executed from. The frequency and number of locations determine how often your web check runs each hour. For example, running from 3 locations every 15 minutes results in 12 web check executions each hour. Web checks are evenly spaced apart, running at 5-minute intervals.

You can choose from 5, 10, and 15 minute frequencies. You can also select multiple global locations where your web check is to be executed from (see image below).

Outage handling

Web checks offer you a few options for alerting you in case of availability outages. With newly created web checks, the setting Generate a problem and send an alert when this web check is unavailable at all configure 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 web check 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 web check 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

Performance thresholds enable you to be proactive about site latency. When enabled, this setting notifies you when a specific action or web check exceeds the threshold from any single location 3 times consecutively. If your web check includes a clickpath with multiple actions, you can set a performance threshold for one or multiple actions. You can enable/disable performance thresholds at any time.

Edit a recorded clickpath

If you've recorded a clickpath, you have further configuration options and can edit the click path, if necessary.

Click the Browse (...) button at the top of the web check page and select Record again to re-record your clickpath. You can also perform local playback to confirm the accuracy of the web check 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 clicking the Details button.

Edit action name

Although we do our best to name actions intuitively, you can edit action names as required.

Add content validation

Content validations help to verify that your web checks load the expected page contents. Content validations are performed through validation rules (see image below). You can define as many validation rules for an action as you want.

You can validate that either a specific text or an HTML element or a text included within an HTML element appears within the action. If it doesn't, the clickpath will fail and the execution will be aborted.

For availability web checks, you can perform content validation by selecting Validate content from the Web check settings menu on the left.

Wait time for action completion

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

Edit locators

In the Advanced action configuration section of action details, you can click Edit locators to specify the CSS and DOM elements to be used during replay.