Dynatrace allows you to easily configure your HTTP monitors when first setting them up and at any time thereafter.
During HTTP monitor creation, configuration settings appear after you have clicked Create an HTTP 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 HTTP monitor
- Select Synthetic from the navigation menu.
- Select the HTTP monitor you want to configure.
- Click the Browse (...) button and select Edit.
- Click through the HTTP monitor options in the left-hand 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.
Within Monitor setup settings you can configure basic monitor properties:
- The URL to check.
- The Name of the monitor—limited to 500 characters.
- The User agent of the request).
- The Max response size—if the response exceeds this size, it is truncated.
Assign HTTP monitor to a web application
This setting is available in edit mode only.
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.
Validation and thresholds
You can validate the response to an HTTP request by checking for specific on-screen text and set a notification to alert you if the response time is unusually long.
Response validation helps you verify that your application loads the expected content by checking if the response contains certain text.
You can set a condition to either pass or fail the monitor based on the results of these checks. If pass criteria are not met (or fail criteria are met), the monitor fails and the execution is aborted.
Select the required option and type in the expected text for reference. Keep in mind that texts are case-sensitive.
Select Interpret content match as regular expression if the specified text is defined as a regular expression.
Performance thresholds enable you to receive notification when response time is unusually long so you can be proactive about site latency. Enter the threshold time in seconds. If the response time exceeds this threshold, a problem is generated and you will receive a notification, as defined in Settings > Integration > Problem notifications.
This setting is available in edit mode only.
Browser monitors offer you a few options for alerting you in case of availability outages. With newly created browser monitors, 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.
Generate a problem and send an alert when this monitor is unavailable for one or more consecutive runs at any location 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.
Retry on error is not available for HTTP monitors.
Frequency and locations
There are two factors that make up your monitoring schedule, how frequently your HTTP monitor runs and from which locations it's executed.
These factors determine how often your HTTP monitor runs each hour. For example, running from 3 locations every 15 minutes results in 12 monitor executions each hour.
You can choose from 1, 2, 5, 10, 15, 30 and 60 minute frequencies.
HTTP monitors must be run from private synthetic locations—see Installing a Synthetic-enabled ActiveGate for details on using ActiveGate for Synthetic Monitoring.
HTTP specific settings
In the HTTP specific settings section, you can configure HTTP requests that the monitor sends to your website. Start with the HTTP method of your monitor as the set of monitor parameters depends on this selection.
HTTP methods supported are:
Enable basic HTTP authentication
Dynatrace makes it easy to automate the login process for password-protected sites. Simply enter your Username and Password.
Accept any SSL certificate
By default, HTTP monitors accept any SSL certificate, regardless of whether they're valid. Deactivate this option to have the monitor fail with invalid SSL certificates.
By default, an HTTP monitor follows all redirects from an original request, until it reaches the final destination. Deactivate this option to monitor only the first response of the redirect chain.
Enable additional HTTP headers
The monitor is created with a bare minimum set of headers required by the protocol. To enable custom headers, toggle Enable additional HTTP headers. Click Add header to provide header type and value.
You can specify multiple HTTP headers, which will be set for all requests the monitor makes.
Set request body
You can send the payload with your POST, PUT, DELETE, and PATCH requests.
To use the request body, you must set up the Content-Type header and specify the type of content you're sending, for example,