Synthetic HTTP monitors can be created to check the availability of resources—websites or API endpoints. In addition, they can be used to check the availability of internal resources that are inaccessible from outside your network.
An HTTP monitor consists of one or multiple HTTP(S) requests (for example, GET, POST, and HEAD requests).
The unit of measure for HTTP monitors is a synthetic request. Each HTTP(S) request consumes one synthetic request.
A synthetic request is charged as soon as the request is made, no matter if it is successful or fails. If a request fails and therefore subsequent requests are not executed, these subsequent requests are not charged.
The following calculation gives you an estimate of the maximum possible consumption, assuming that all Synthetic requests were executed. Actual consumption may vary depending on if some requests failed subsequent requests were not executed.
# Synthetic requests consumed per monitor = (# Synthetic requests included in monitor) × (# Executions per hour) × (# Locations) × # Hours
This section describes the different Dynatrace tools that you can use to track consumption and costs.
Dynatrace provides built-in usage metrics that help you understand and analyze your organization's consumption of Real User Monitoring.
For details about the respective monitoring consumption metrics, see Built-in Real User Monitoring metrics.
You can also view your usage in Account Management. Go to Account Management > Subscription > Overview > Cost and usage details > Usage summary and select the HTTP Monitor capability.
You can query metrics via the Environment API - Metrics API v2.