HTTP monitors for private locations (public Beta)

Dynatrace is happy to announce the public beta release of one of our most requested features, availability monitoring for internal applications. We’re extending our synthetic monitoring offering by introducing a new type of synthetic monitor: HTTP monitors. With HTTP monitors, you can monitor the availability of individual URLs and API endpoints.

Create HTTP monitor from Synthetic tab

What are HTTP monitors?

An HTTP monitor uses a simple HTTP request to monitor the availability of a given URL. The request is executed with a set of specified parameters:

  • HTTP method
  • HTTP headers
  • User agent

HTTP monitors also support:

  • Response validation
  • Basic authentication
  • Monitoring of POST data
  • Redirect follows
  • SSL certificate acceptance
  • Assignment to specific applications

You can also define a Performance threshold that will be displayed along with response time analysis and Max response size that will be taken into account while downloading and parsing data.

For full details, see How do I create an HTTP monitor? and HTTP monitor setup configuration.

Configure HTTP monitors (public Beta)

HTTP monitors are lightweight as they don’t involve a browser in the monitoring process.

It’s currently only possible to execute HTTP monitors from private locations you define within your infrastructure. Private synthetic monitors are executed from ActiveGates that have synthetic monitoring available that serve as locations for synthetic monitors.

To enable synthetic for an ActiveGate, log into your ActiveGate via terminal, find the file (in/var/lib/dynatrace/gateway/config or /var/lib/dynatrace/gateway/gateway/config, depending on your ActiveGate version and installation type) and add or modify the following section as shown:

synthetic_enabled = true

This functionality is specific to the public Beta, as the final version of HTTP monitors will be configured and managed directly from the Dynatrace UI.

Once you’ve edited or pasted in the lines above, you must restart the ActiveGate. For full details, see ActiveGate configuration for HTTP monitors.

Your ActiveGates may be now assigned to custom locations that can be configured at Settings > Web & mobile monitoring > Custom monitoring locations.

Upon each execution, an HTTP monitor collects a set of results for further analysis and reporting such as availability, response time, HTTP status codes, response size, and outage error messages.

When HTTP monitors detect an anomaly with the availability of a given URL, a new problem is generated and appropriate alerts are sent out.

HTTP monitors are the perfect tool not just for lightweight monitoring of your websites, but also for single API endpoints. With this in mind, we’re pleased to announce that we’ve already started working on multi-step HTTP monitors that allow you to execute entire API scenarios, including authentication, parsing responses, and the passing of parameters between steps. This is a perfect solution for mobile app API availability monitoring.

Beta limitations & requirements

  • HTTP monitors are only available on Linux ActiveGates.
  • At the moment, only two ActiveGates can be assigned to a single location for load balancing and failover.
  • HTTP monitors support only IPv4 network configuration and DNS UDP.
  • Minimum hardware requirements are the same as for a clean ActiveGate installation.

Providing feedback

Your feedback is very valuable to us, and we look forward to hearing from you with suggestions and ideas.