Internet health map — REST API

The Internet health map provides a geographic view of Backbone and Last Mile performance that gives you a near real-time view of the global user experience. This enables you to quickly determine if the performance issues in a particular geographical area are part of a broader Internet slow-down. Backbone and Last Mile metrics are compared to baseline values and a status indicating how performance compares is displayed on the Internet health map.

This resource returns the current and historical Internet health map Data, both the current and the baseline data. It returns response time, DNS time, connect time, content time, throughput, the number of good pages, the total number of pages, and the number of connections for the nodes used to build the Dynatrace Synthetic Monitoring Platform’s Internet health map.

Resource path

GET <server>/publicapi/rest/v1.0/healthmap

In the resource path above, the <server> address is https://datafeed-api.dynatrace.com.

URL parameters

Name Type Required Default Description
time Long No See description The metric’s current value is calculated as the average value from the past hour with the past hour calculated up to the previous :00 minutes. For example, if the time is 9:44 am, then the average hourly value is calculated from 8:40 am - 9:40 am. The metric’s baseline value is calculated as the metric’s average value over the same time period for the past four weeks. For example, if the day/time is Friday at 9:44 am, then the baseline is calculated as the average value for the current hour (9:00 am - 10:00 am) for the past four Fridays. If no time is provided the current hours data is returned. If time is provided the hour in which the time is represented will be returned. (Historical data is provided for 14 days.)

HTTP request header parameters

Header Name Allowed Values Required Description
Accept application/json
or
application/xml
No Determines the content type of the response data. The API supports JSON, XML and CSV. The default is JSON.
Authentication bearer <accessToken> Yes This header is required and must contain the access token returned by a login request. The bearer keyword and space is required before the token.
Content-Type application/xml;charset=UTF-8 No Defines the content type the REST API accepts in the request payload. The only supported format is XML in UTF-8 encoding.

Sample request

Sample responses