The browser monitors reporting provides:
To display browser monitor results
The top panel shows overall monitor availability and performance for the selected timeframe.
Use the filter bar at the top of the page to filter browser monitor executions by one or more locations.
Under the filter bar, you can see tiles for important information:
In the upper-right corner of the page, you can access Analyze executions, On-demand execution, and more browser monitor settings:
To see details for a specific execution
Select Analyze executions at the top of the monitor's details page.
You are directed to the Multidimensional analysis page in previous Dynatrace.
In the Detailed analysis timeframe section, select an execution to pin its tooltip.
Hover over the tooltip and select View execution.
The Availability card displays the monitor's availability for the selected timeframe, either aggregated for all locations or for each location separately. It contains information about all availability problems related to the given monitor, maintenance windows, and unfinished executions. The problems are displayed as bar-shaped notifications over the availability chart. They provide the problem details and mark the period when the problem occurred.
Also, if the monitor is down (unavailable) at one or more locations, the outage (downtime) duration and affected locations are displayed in the metric visualizations above the Availability card.
A monitor can be down at one or all locations. Several downtimes may occur in a given timeframe. Their durations are summarized to calculate the total outage (downtime) duration. Overlapping downtimes are not counted.
Availability metrics are calculated by dividing the number of successful executions ("up") by the total number of executions
Determine the number of up executions in the timeframe.
This is the total number of executions in the timeframe, minus the number of failed ("down") executions in the timeframe.
Determine availability.
Divide the number of up executions by the total number of executions, and then multiply by 100 to get a percentage.
Example
Suppose we have 5 down executions in a 35-minute timeframe.
35
.5
.35-5 = 30
.(30/35) \* 100 = 0.8571 \* 100
= 85.71 percent
.You can set up a maintenance window so test executions are not suppressed during maintenance periods. Then, if outages happen during the maintenance period, down executions are included in the metrics calculations.
In the example below, the availability is less than 100% because the down executions are included in the metric calculation by default.
timeseries av = avg(dt.synthetic.browser.availability), by: {dt.entity.synthetic_test}| fields dt.entity.synthetic_test, avgAV=arrayAvg(av)| filter dt.entity.synthetic_test == "SYNTHETIC_TEST-2891B733D75330FA"
To exclude the maintenance period executions from the metric calculation
dt.maintenance_window_ids
dimension to the query.isNull(dt.maintenance_window_ids)
.In the example below, we observed down executions during the maintenance period. However, they were not included in the calculation metric because we used the dt.maintenance_window_ids
dimension along with the isNull(dt.maintenance_window_ids)
filter condition.
timeseries av = avg(dt.synthetic.browser.availability), by: {dt.entity.synthetic_test, dt.maintenance_window_ids}| filter dt.entity.synthetic_test == "SYNTHETIC_TEST-2891B733D75330FA"| filter isNull(dt.maintenance_window_ids)| fields avgAV=arrayAvg(av)
The approach described above requires all executions to happen at the same rate. However, in a real-world environment this is not always the case as the monitor execution frequency may change or additional on-demand executions may be triggered.
To make the calculation more accurate, the interpolation mechanism is introduced: 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.
To see interpolated data points, add the interpolated
dimension to the query.
timeseries avg(dt.synthetic.browser.availability), by:{dt.entity.synthetic_test, interpolated}| filter dt.entity.synthetic_test == "SYNTHETIC_TEST-7E0A1CF206C4A1C5"
The result below shows the blue data points that coincide with actual executions, and the white data points which don't.
Let's imagine a monitor is set to execute tests every five minutes. So, every fifth data point (blue) coincides with an actual execution. All data points following the first down execution and preceding the first up execution count as "down". Thus, when calculating the availability metrics, the number of down executions is calculated as follows:
Down executions = the first actual down execution + all following "down" data points.
Also, the Availability card displays notifications over the availability chart. The notifications show details of a maintenance window, outages, and not executed or finished tests. A notification is displayed as a bar above the timeframe when a maintenance window was applied, an outage occurred, or some tests were not executed or finished. Hover over the bar to see the details:
Browser monitor local outage—the outage happened in one or more locations from which the monitor executed the tests.
Browser monitor global outage—the outage happened in all locations from which the monitor executed the tests.
To see the details of the problem
Select the bar to pin the Browser monitor local outage or Browser monitor global outage tooltip.
Hover over the tooltip.
Select View problem details.
Select one of the available options:
Maintenance window—a maintenance window was on in the timeframe.
To see the maintenance window
Select the bar to pin the Maintenance window tooltip.
Hover over the Maintenance window tooltip.
Select View maintenance window settings.
Select Settings Classic.
If some tests were not executed or finished due to improper monitor configurations or some issues at Dynatrace side, you can see a reason behind it:
No result—the execution started but the results were not delivered. Reach out to the Dynatrace support team.
No capability—you're trying to execute monitors that aren't supported by a location (for example, NAM ICMP monitors - from a location with inactive ICMP).
Discarded, not executed—the probable cause is the overloaded private location. Check the capacity metrics. If there are no issues with the metrics, contact the Dynatrace support team.
The Performance card displays:
It helps identify slow steps or regional performance issues.
Only performance problems are marked in this section.
If the monitor violates a performance threshold, whether for the total duration of all steps or for the duration of an individual step, a solid red line appears above the performance graph for the problem duration. Select the solid red bar to display a link to the problem overview page.
The Problems card shows performance (threshold violation) and availability (local or global outage) problems.
There are three main problem types for browser monitors:
Performance problems may combine threshold violations at the monitor as well as step levels.
The problems section lists all problems in the selected timeframe, both open and closed. On top of that, you can:
Problems, along with their constituent events give you a full picture of the number and scope of your monitor's issues.
The Synthetic steps and actions card shows details for each browser step the monitor is set to perform. It can be a page loading, click on some button or any other control, etc. For each step, you can see such details as:
Select the expand icon for a step to see the response time of individual executions in a specific timeframe (for example, the last hour). It allows you to evaluate the overall step performance. The expand icon is unavailable and can't be selected if there is no performance data for the step.
The Errors card displays errors found in the selected timeframe.
On the card, you can:
See the details of an error in the form of a table with the step and number of occurrences.
Select Analyze errors .
You are directed to the Multidimensional analysis page in previous Dynatrace where you are provided with in-depth error analysis.
The Events card shows all events that compose problems. Events for active as well as resolved problems show up in the list and timeline.
Hover over a time slot in the event timeline to see the type and number of events generated at that interval. Select a time slot to view a tooltip with the events that took place in it.
Select an event type to see the list of events. An event is created per location where, for example, your monitor violates step- or monitor-level performance thresholds. Select an individual event to see details.
The Locations card shows the status of the last monitor execution for each location. The status is displayed with colors:
This informational card shows the number of steps, the number and list of locations, frequency of monitor execution, and any applied tags.
Select Edit to edit or apply additional tags.