NAM monitors results reporting
- Latest Dynatrace
- Reference
- 2-min read
On-demand monitor execution via web UI is available as part of DPS license only. The retention period for data from monitor execution is 35 days.
For Non-DPS license users, monitor execution is possible via API. You can access the results for the last 6 hours.
To display a reporting page for your monitor, select View details in upper-right corner of the preview panel.
The default reporting pages consists of:
-
Tiles displaying information at a glance about global outages, active issues, number of affected locations, availability, total downtime, and duration.
-
Availability—a chart of availability over time. Availability for NAM monitors is calculated by comparing the request success rate to defined constraints. A period when availability is 0% is called an outage.
You can narrow the chart's time range to cover just the outage period. This allows you to identify, for example, requests that negatively impact availability. By default, the availability chart is collapsed when showing 0% or 100% for the whole time range. To open it, simply select Availability.
-
Success rate—a chart of the success rate over time, where the success rate is the percentage of all executed requests that were sucessful.
- See the conditions a request needs to meet to be considered successful.
- Select the Show requests button under the chart to see availability changes such as the average performance, average availability, and packet success rate (this column is only available for ICMP).
-
Performance—a chart of performance over time, where performance is calculated as an average for all successful requests. Note that performance metrics are not reported for failed requests.
-
Changes—a history log that displays:
- When the monitor was created and who created it.
- Who changed the monitor properties, when the change was made, and which properties were changed in the selected timeframe.
Total downtime calculation
The total monitoring time is divided into minute-level data points. All data points count as executions, although they don't necessarily coincide with actual executions.
In the following example, the blue data points coincide with actual executions, and the white data points don't.
For example, if a monitor is set to execute tests every five minutes, every fifth data point (blue) coincides with an actual execution. All data points following the first failed ("down") execution and preceding the first successful ("up") execution count as "down." Thus, the total downtime is calculated as follows:
Total downtime = the first actual down execution + all following down data points.
