To configure an existing web check:
- Click the Web checks tile on the home dashboard.
- Select the web check you want to configure.
- Click Edit web check.
Define a 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 run 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 spaced apart, running at 5-minute intervals.
You can select from 5, 10, and 15 minute frequencies and 13 global locations:
- New York
- San Jose
- São Paulo
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. If you disable performance thresholds, you can re-enable them at any time.
Web checks offer you a few options for alerting you to availability outages. With newly created web checks, the Alert if the web check is not available at all configured locations setting is enabled by default. This setting alerts you of an availability outage if all locations are seeing outages.
The second option allows you to choose the number of locations that an outage can be observed from as well as the number of consecutive occurrences. With the settings shown in the image below, a problem will be generated if 3 out of 5 locations are unable to access your site through two rounds of consecutive executions.
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.
Bypass login forms
With LoginSense TM technology, Dynatrace can intelligently and securely log into your web application each time a web check runs. This feature is only an option for availability web checks and is meant to provide easy monitoring of password-protected pages.
Note that login bypass doesn’t work with basic authentication. With basic authentication you need to record a clickpath web check
Re-recording a clickpath
Following clickpath recording you’ll see a Record again button in the top header of this page. Click to re-record your clickpath using the same URL.
Edit your clickpath
You can enable local playback by clicking the Validate clickpath button. This feature ensures that your recorded clickpath plays back as expected.
If necessary you can delete unnecessary actions from your clickpath.
Edit action name
You can drill down into individual actions to edit them. For example, we do our best to name actions intuitively, but you can edit action names as necessary.
Add content validation
Content validations help to verify that your web checks load the expected page contents. You can add as many validations for an action as you want.
Your first validation option is to validate text across all content downloaded during an action.
Simply enter text and click Save. This will validate that the specified text appears within the action. If it doesn’t, the click path will fail and stop execution.
The second option is validation against a specific element. With this option you ensure that a specific HTML element is loaded within a page. You can optionally specify the text you are interested in validating against within the element.
You’ll notice two additional check boxes for both validations that can also be used to validate text.
- Fail if this text is loaded in this action is useful for checking for custom error pages. The clickpath will fail if the specified text or element appears.
- Interpret as regular expression interprets specified text as a regular expression, allowing you to validate against dynamic content such as order numbers or search results.
Wait time before execution of next action
Though Dynatrace automatically selects an appropriate wait type for each action, you can customize the wait time for any individual action.
- Wait for page to load completely waits for network activity to be completed after the load event has been triggered. This is the default wait used when loading a new page.
- Wait for background network activity to complete waits for all network activity to be complete after the action. This is the default wait used for XHR requests and interaction within single-page applications.
- Wait for specific period of time allows you to specify the number of seconds you’d like to wait between this action and the next.
- 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.