Using the Network Overview
When you create any test in which you include network measurements – such as network, HTTP server, page load, or DNS server tests - you get access to the Network Overview section. The Network Overview leverages the ThousandEyes standard layout.
This article highlights the elements of the Network Overview.
The screenshot below shows the Network Overview of a page load test:
There are three metrics available in the metric selector section of the interface:
- Loss: packet loss expressed as a percentage of packets sent
- Latency: average latency between endpoints
- Jitter: variation in latency over time
Tests running from enterprise agents that include the bandwidth measurements option will also show a Bandwidth metric.
The Network Overview shows two different data views, depending on whether an agent location is selected. These are shown below.
Without a location selected
The computed averages area displays the worldwide average of each selected metric, at the date/time selected in the interface.
Without an agent selected, the timeline shows a chart showing the average based on the selected metric, calculated across all locations. An example of the global chart for the loss metric is shown below:
The detailed metrics area shows by-location metrics for each of the available metrics, in a tabular view. You can sort the table by clicking the table header.
With a location selected
The computed averages area displays the location-based average of each selected metric, at the date/time selected in the interface.
With a location selected, the timeline shows a chart showing the average based on the selected location, charted against the global values for the same metric. An example of the location chart for the loss metric is shown below:
The detailed metrics area shows by-location metrics for each of the available metrics, in a tabular view. The table can be sorted by clicking the table header. The selected location will be shown highlighted in the table. The sample table below is sorted in descending order for packet loss and with the Buenos Aires, Argentina Cloud Agent selected.
Last modified 1yr ago