Dashboards and Reports

Search…
The ThousandEyes platform contains a reporting engine that provides both on-demand reports and scheduling of automatically generated reports. Data from tests can be organized into highly customized layouts, presented numerically or in tables or graphs, and sent via email to users.
Widgets
A report consists of one or more report widgets. ThousandEyes currently provides the following types:
Numbers
Tables
Multi-metric tables
Pie chart
Stacked bar/column chart
Grouped bar/column chart
Time series
Stacked bar chart
Map
Color grid
Box-and-whiskers
You create a report by selecting the widgets appropriate for the data you wish to include, and then configuring the parameters of the widgets. Widget parameters allow for operations on the raw test data such as statistical calculations (for example, means, medians, or percentiles), data trends, and tabular views of the data. Widget configuration also permits arrangement of the numbers, tables and time series graphs on the page. Once configured, reports permit the user to select a time frame of interest, and the report page will then be populated with that period's test data according to the report configuration.
With each report you can take report snapshots. Report snapshots are analogous to test view snapshots. The snapshot represents a specific time range of the report’s data. Report snapshot creation can be scheduled at regular intervals. Additionally, the report snapshot can be automatically emailed to a list of recipients.
Report data can also be shared through embedded widgets, which allow a report's widgets to be included in customer web pages such as kiosk displays or network operations center dashboards. For more information on embedded report widgets, see Embedding Report Widgets in External Web Sites.
Configuring Reports
The Reports page (Reports > Reports) allows you to create, modify and delete reports, and create and schedule snapshots of existing reports. The figure below and the following list describe the report configuration tool on the Reports page. Below the list is the Creating a New Report section with steps for creating a report.
1.
Recent Snapshot Selector: This drop-down menu provides a list of most recent snapshots for each report in account group.
2.
Report selector: This drop-down menu provides a list of existing reports, along with a Search field to search the list.  Select a report to view by clicking the report name. A watch icon  (
) next to the name of a report indicates that report has scheduled snapshots. A shared by icon (
) next to the name of report indicates that report has been shared with other account groups in the same organization. A shared with icon (
) next to name of report signifies the report belongs to a different account group in same organization. An option to perform Bulk Actions enables creating multiple report snapshots or deleting multiple reports at once.
3.
Report Time Range selector: Quickly select relative time ranges (for example, Last 7 days), fixed time ranges (for example, This Month) or configure a custom time range. Time ranges are displayed using the time zone configured within the user's profile. By default, data for the last 1 day is displayed. Widgets with a configured Fixed Time Span option are unaffected by the time range selector.
4.
Snapshots menu provides the following options:
Save a Snapshot: The currently selected report will be saved as a snapshot, using the time range configured in the Time Range selector.
Schedule a Snapshots: The currently selected report can be saved as a snapshot on a daily, weekly or monthly basis.
5.
Add Widget: Opens the Add Widget side panel. New widgets can be added to the report.
6.
Options button provides the following options:
Create New Report: Creates a new blank report to be named and populated with widgets
Duplicate Report: Creates a copy of the currently viewed report, to be renamed and modified
View Report Details: Allows a user to edit the currently viewed Report Name, Account Group Visibility and metadata. The Related Snapshots History section shows list of most recent snapshots as seen in the screenshot below.
​
Download as PDF: Download the report as a PDF file. Timestamps will be displayed using the time zone configured for the organization.
1
Note: The download button options are not visible if a rendering is limited for the report widget. 
Copied!
Download as CSV: Download the report as a CSV file. Timestamps will be displayed using the time zone configured for the Organization.
Delete Report: Delete the currently viewed report.
Creating a New Report
Follow these steps to create a new report:
1.
On the Reports page, click on the Options button and select Create New Report.
2.
Enter a report name in the Report Name field.
3.
Enter appropriate Report Description.
4.
Configure desired Account Group Visibility, below are available options:
All account groups: make report visible to all account groups in current organization.
Only current account group: hide report from other account groups.
Specific account groups: make report visible to desired account groups, which can be selected from resulting drop-down menu.
5.
Set as my default: Check this box to make this report the default report displayed for the current user.
6.
Set as default for account group: Check this box to make this report the default report displayed for the current account group.  The user's default takes priority over the account group's default. You cannot set a report that is shared from another account group as your default. 
7.
Click Create Report to open up widget manager.
​
​
Reports are created in the widget manager, which can also be used to modify a report. Invoke the widget manager by clicking the Add Widgets button from the Reports page. The figure below and the following list describe the features of the widget manager.
1.
Widget Picker: Select a widget to add to your report by either clicking on the type of widget desired or by dragging it to the location within the report layout where you wish the data to appear. 
2.
Widget Configuration: Once you select a widget, a widget configuration panel will open. You can minimize this panel and move it as needed.
3.
Add Another Widget: Click this button to add another widget from the widget picker side panel. 
4.
Cancel Changes: After you make updates to your widget configuration, you can preview those changes before saving them. If you don't like the changes you have made, click the Cancel button and the changes will revert. 
5.
Save Changes: Confirm the changes you have made to your widget configuration. 
6.
Widget Configuration: Click the gear icon to bring back up the widget configuration side panel.
7.
More Actions: Click the More Actions icon to delete, duplicate, embed or rename the widget (available inside or outside the widget manager) or download a PNG or JPG image of the widget.
8.
Widget handle: Click the widget handle to change the size of the widget to either half or full page width (available only in the widget manager). 
To add widgets to the report, click the Add Widget button and open up the widget selector side panel. Widgets can be dragged to different positions within the overall report page whenever the mouse pointer is moved over the header of a widget, or by clicking on the widget icon.
Once the widget is added to the report, select appropriate values for each available option. Changes made in the widget manager are immediately saved, allowing for exit of the widget manager at any time with a single click.
Working with Report Widgets
Consider the following when choosing and configuring report widgets:
Number widgets display a single scalar quantity, such as an average of packets lost or page load times, or a number of alerts.
Table widgets permit a breakdown of numbers by rows and columns. Either rows or columns can list by test, country, continent, or data source (agents or BGP monitors) or the aggregate of those ("All").
Multi-metric table widgets allow for the same configuration as Table widgets, but can have columns with different metrics, rather than a single metric for the entire table.
Stacked bar/column chart widgets provide horizontal histogram bars with multiple values, which are useful for composite metric data (such as HTTP response or fetch time) and for comparing values between multiple tests, or comparing values on a per-country basis. Bars can be oriented horizontally or vertically as columns.
Grouped bar/column chart widgets are similar to stacked bar chart widgets, but represent multiple values as single bars in a group of bars. Bars can be oriented horizontally or vertically as columns.
Pie chart widgets are similar to stacked bar chart widgets, representing multiple values as proportionally sized segments of a pie.
Time series widgets are line plots with time on the horizontal axis, and the selected quantity on the vertical axis.
Time series stacked area widgets are line plots with time on the horizontal axis, and the selected quantities on the vertical axis. They are used similarly to stacked bar charts but showing values over time.
Map widgets display data on a world map, based on location of the testing systems (agents or BGP monitors). Data can be displayed per country, per continent, or per agent (if a non-BGP metric is displayed).
Color grid widgets shows an array of colored cards, where each card's color depends on the configured scale. See Customizing your Dashboard for more information on Color Grid. 
Box-and-whiskers widgets plot data values versus time on the horizontal axis, with the vertical axis displaying the median, minimum and maximum data points per time value, along with a bar for the range of values represented by the second and third quartiles.
To add widgets to a report, click +Add Widgets on the Reports page to enter the widget manager. Modifying an individual widget's settings can be done from the Reports page by clicking the gear icon. Details of the settings for each widget type are below, along with examples.
Number Widget
The image below shows an unconfigured number widget.
Number widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For example, agent-to-server tests have five metrics: Available Bandwidth, Capacity, Jitter, Latency and Packet Loss. In addition to each of the ThousandEyes test types, Alerts is also a category of choices for metrics. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean?​
Measure: A statistical measurement. Measure choices available depend on the Metric setting, but will come from the following list:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
Maximum: The maximum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
Standard Deviation: The population standard deviation of a set of measurements, such as the latency times of a Network test over the time period of the report.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were from 0 to 500 ms.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP server test indicate the total number of HTTP server alerts received in the reporting period.
Active Time: The amount of time an alert rule was active. (Alerts metrics only)
Inactive time: The amount of time an alert rule was inactive. (Alerts metrics only)
Show Comparison to Previous Timespan: When checked, the report displays the difference between the current data set and the previous data set of the same length as the reporting interval. The comparison numbers are shown as an additional row of cells below the principle row, in red or green font color along with an up-arrow or down-arrow indicating a numerical increase or decrease. The combination of color and arrow direction changes based on the metric setting. For some settings of metric, a numeric increase is a change for the better and thus is rendered in green. For other metrics a numeric increase is a change for the worse and rendered in red. For some metrics, the situation may be ambiguous; those metrics are rendered in grey font.
"N/A" is displayed in place of the comparison numbers when sufficient data from the previous reporting interval is not currently available for a comparison (such as when a test is first configured but hasn't accumulated a full timespan of data). A "-" (single dash) is displayed in place of the comparison numbers when no data is present and will not ever be present, such as when a agent is not assigned to the test.
By default, the timespan of the past data set is the timespan prior to the current data set's time span, which is specified by the From and To fields of the report's date and time selector. If the Fixed Time Span box is checked, then the timespans of the data sets are specified by the Fixed Time Span setting's date selector.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Card Description: For number widgets, each number is contained on a card, which can be given its own description which will appear in the number box when viewing the report. Configuration of this setting is optional.
Tests: Names of tests that will provide the data to the report. Select one or more tests that is appropriate to your Metric setting (e.g. if the Metric is Packet Loss, select one or more Network tests or tests with included Network metric; if the Metric is Response Time, select an HTTP Server or Page Load test).
Sources: Filter sources from which the data will be taken. The column heading changes based on which Metric is set, and will be one of the following:
Alert Rules: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of alert rules.
Agents: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agents.
Agent Labels: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agent labels (Built-in or Custom).
Tests: For any Metric, a list of tests.
Test Labels: For any Metric, a list of test labels (Built-in or Custom).
Monitors: If the Metric is a BGP test or alert, a list of ThousandEyes BGP monitors.
Example Number Widget
Below is an example of a configured number widget and the resulting report output.
The configuration shows the widget configured with three numbers:
1.
Maximum Packet Loss for selected agent-to-server test.
2.
Total number of alerts triggered across all tests.
3.
Maximum Packet Loss observed by Endpoint Agents across all browser sessions.
Table Widget
The image below shows an unconfigured table widget.
Table widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from Platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For example, agent-to-server tests have five metrics: Available Bandwidth, Capacity, Jitter, Latency and Packet Loss. In addition to each of the ThousandEyes test types, alert also have metrics. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean? Depending on your choice of Metric, the names of the widget settings may change, or additional settings may appear. For example, selecting any of the alerts metrics will result in the Alert Rules setting appearing in the widget.
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
Maximum: The maximum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP Server test indicate the total number of HTTP Server alerts received in the reporting period.
Active Time: The amount of time an alert rule was active. (Alerts metrics only)
Inactive time: The amount of time an alert rule was inactive. (Alerts metrics only)
Show Comparison to Previous Timespan: When checked, the report displays the difference between the current data set and a past data set, shown as an additional row of cells below the principle row, with the comparison numbers in red or green along with an up-arrow or down-arrow indicating a numerical increase or decrease. The combination of color and arrow direction changes based on the metric setting. For some settings of metric, a numeric increase is a change for the better and thus is rendered in green. For other metrics a numeric increase is a change for the worse and rendered in red. For some metrics, the situation may be ambiguous; those metrics are rendered in grey font without accompanying arrows.
"N/A" is displayed in place of the comparison numbers when sufficient data is not currently available for a comparison (such as when a test is first configured but hasn't accumulated a full timespan of data). A "-" (single dash) is displayed in place of the comparison numbers when no data is present and will not ever be present, such as when a test error prevented a round of data collection.
By default, the timespan of the past data set is the timespan prior to the current data set's time span, which is specified by the From and To fields of the report's date and time selector. If the Fixed Time Span box is checked, then the timespans of the data sets are specified by the Fixed Time Span setting's date selector.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Limit To: When checked, the table rows will display at most the number you set in the selector. When more rows exist than are displayed, the Sort By order determines which rows are displayed.
Rows:
Agent: Data from all agents are aggregated by agent. A row is displayed for each agent that has data from at least one test.
All: Data from all sources are aggregated into a single row.
Continents: Data from all sources are aggregated by continent. A row is displayed for each continent that has data from at least one source.
Countries: Data from all sources are aggregated by country. A row is displayed for each country that has data from at least one source.
Test: Data from all tests are given their own rows.
Test Labels: Data from all test labels are given their own rows. 
Agent Labels: Data from all agents aggregated based on agent labels.
Columns:
Agent: Data from all agents are aggregated by agent. A column is displayed for each agent that has data from at least one test.
All: Data from all sources are aggregated into a single column.
Continents: Data are aggregated by continent. A column is displayed for each continent that has data from at least one source.
Countries: Data are aggregated by country. A column is displayed for each country that has data from at least one source.
Test: Data from all sources are aggregated by test. A column is displayed for each test that has data from at least one source.
Sort By: For tables containing multiple rows, the Sort By setting will determine in what order the rows appear. That is, the value of the Sort By setting is applied to the value in the Rows setting.
Default: Sort rows optimally, based on the settings for Metric and Show Comparison. The metric that is optimal for your settings is shown in parentheses.
Alphabetical: Sort rows by ascending alphabetical order.
Alphabetical (Reverse): Sort rows by ascending alphabetical order.
Greatest Decrease: Sort rows by greatest decrease between current and past measurements of a row's Metric value. This setting is meaningful only when the Show Comparison box is checked.
Greatest Increase: Sort rows by greatest increase between current and past measurements of a row's Metric value. This setting is meaningful only when the Show Comparison box is checked.
Highest: Sort rows by highest value first.
Lowest: Sort rows by lowest value first.
Tests: Names of tests that will provide the data to the report. Select one or more tests that are appropriate for your selection of Metric setting (e.g. if the Metric is Packet Loss, select one or more Network tests or tests with included Network metrics; if the metric is Availability, select a Web test, etc..)
Sources: Filter the sources from which the data will be taken. This setting's name and the corresponding column heading change once the Metric is set, and will be one of the following:
Alert Rules: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of alert rules.
Agents: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agents.
Agent Labels: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agent labels (Built-in or Custom)
Tests: For any Metric, a list of tests. 
Test Labels: For any Metric, a list of test labels (Built-in or Custom).
Monitors: If the Metric is a BGP test or alert, a list of ThousandEyes BGP monitors.
Example Table Widget
Below is an example of a configured table widget and the resulting output.
1.
The configuration shows Cloud and Enterprise Agents set as data source, with latency of agent to agent tests set as a reported metric for the table. The widget is set to visualize Standard Deviation of a latency metric in the source-to-target direction.
2.
Data is set to visualize with tests forming the Rows and agent forming the columns. Rows are sorted by a reported value, in the ascending order.
3.
The filter is set to include 2 of 189 available agent to agent tests. The “+” icon can be used to put on additional filters.
Multi-Metric Table Widget
The images below show an unconfigured multi-metric table widget. The first image displays the Rows tab, and the second image displays the Column tab.
Rows Tab
The multi-metric table widget's Rows tab has the following settings:
Rows: Select the property that will be used for the rows in the table. Rows will be one of the following:
All: Any property that is relevant to the criteria in the Column(s) tab(s) will be used as a row.
Tests: Tests relevant to the criteria in the Column(s) tab(s) will be used as a row.
Test Labels: Test labels relevant to the criteria in the Column(s) tab(s) will be used as a row.
Agents: Agents relevant to the criteria in the Column(s) tab(s) will be used as a row.
Monitors: Monitors relevant to the criteria in the Column(s) tab(s) will be used as a row.
Agent Labels: Agent labels relevant to the criteria in the Column(s) tab(s) will be used as a row.
Servers: Servers relevant to the criteria in the Column(s) tab(s) will be used as a row.
Countries: Servers relevant to the criteria in the Column(s) tab(s) will be used as a row.
Continents: Continents relevant to the criteria in the Column(s) tab(s) will be used as a row.
Sort By: For tables containing multiple rows, the Sort By setting determines in what order the rows appear. That is, the value of the Sort By setting is applied to the value in the Rows setting.
Default: Sort rows optimally, based on the settings for Metric and Show Comparison. The Metric that is used for each column shows the column's Measure in parentheses.
Alphabetical: Sort rows by ascending alphabetical order.
Alphabetical (Reverse): Sort rows by ascending alphabetical order.
Greatest Decrease: Sort rows by greatest decrease between current and past measurements of a row's Metric value. This setting is meaningful only when the Show Comparison box is checked.
Greatest Increase: Sort rows by greatest increase between current and past measurements of a row's Metric value. This setting is meaningful only when the Show Comparison box is checked.
Highest: Sort rows by highest value first.
Lowest: Sort rows by lowest value first.
Show Comparison to Previous Timespan: When checked, the report displays the difference between the current data set and a past data set, shown as an additional value in the cells below the principle value, with the comparison numbers in red or green along with an up-arrow or down-arrow indicating a numerical increase or decrease. The combination of color and arrow direction changes based on the metric setting. For some settings of metric, a numeric increase is a change for the better and thus is rendered in green. For other metrics a numeric increase is a change for the worse and rendered in red. For some metrics, the situation may be ambiguous; those metrics are rendered in grey font without accompanying arrows.
"N/A" is displayed in place of the comparison numbers when sufficient data is not currently available for a comparison (such as when a test is first configured but hasn't accumulated a full timespan of data). A "-" (single dash) is displayed in place of the comparison numbers when no data is present and will not ever be present, such as when a test error prevented a round of data collection.
By default, the timespan of the past data set is the timespan prior to the current data set's time span, which is specified by the From and To fields of the report's date and time selector. If the Fixed Time Span box is checked, then the timespans of the data sets are specified by the Fixed Time Span setting's date selector.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Limit To: When checked, the table rows will display at most the number you set in the selector. When more rows exist than are displayed, the Sort By order determines which rows are displayed.
Sources: Filter sources from which the data will be taken. This setting's name and the corresponding column heading change once the Metric is set, and will be one of the following:
Alert Rules: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of alert rules.
Agents: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agents.
Agent Labels: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agent labels (Built-in or Custom)
Tests: For any Metric, a list of tests. 
Test Labels: For any Metric, a list of test labels (Built-in or Custom).
Monitors: If the Metric is a BGP test or alert, a list of ThousandEyes BGP monitors.
Servers: For any Metric, a list of servers being tested.
Location: For any Metric, a list of locations being tested.
​
​
Columns Tab
The multi-metric table widget's Columns tabs have the following settings:
Metric: Each type of ThousandEyes test has its own metrics. For example, agent-to-server tests have five metrics: Available Bandwidth, Capacity, Jitter, Latency and Packet Loss. In addition to each of the ThousandEyes test types, alerts also have metrics. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean? Depending on your choice of Metric, the names of the widget settings may change, or additional settings may appear. For example, selecting any of the alerts metrics will result in the Alert Rules setting appearing in the widget.
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
Maximum: The maximum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the latency times of a Network test over the time period of the report.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP Server test indicate the total number of HTTP Server alerts received in the reporting period.
Active Time: The amount of time an alert rule was active. (Alerts metrics only)
Inactive time: The amount of time an alert rule was inactive. (Alerts metrics only)
To add a column, click on the Add New Column link. To delete a column, click the tab of the column you wish to delete, then click the X in the column's header.
Example Multi-Metric Table Widget
Below is an example of a configured multi-metric table widget entitled “HTTP Server statistics” and the resulting output.
The Rows setting is set to "Tests", indicating that the table's rows will be individual test names, and the Sources is set to filter on "Tests", where 3 tests of 241 are selected, creating a two-row table with the first column containing those two selected tests. Column 1 has "Availability" selected as the Metric and "Mean" as the Measure. Each test row will display the mean of availability in the first column. Column 2 has "Response Time" selected as the Metric and "Maximum" as the Measure. Each test row will display the largest of all response time values in the round, in the second column.
Sort by is set to "Default (Tests)", meaning that the sorting order of the rows will be the default (the first column that's set by the Rows). The dark switch with the white up-arrow indicates that the value of the Sort by field will be sorted from low to high, alphabetically in this case. The Show Comparison box is checked, producing the second, lower set of numbers along with up or down arrows to indicate whether the value rose or dropped, and a color code to indicate whether that rise or drop is an improving change from the previous period (green), a degrading change (red) or is ambiguous (gray). Fixed Time Span is unchecked, indicating that the report uses the time frame that is set at the top of the Reports page. Limit To is set to 2 rows, thereby preventing one of the three tests from being displayed.
Time Series Widget
The image below shows an unconfigured time series widget.
Time series widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from Platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For example, agent-to-server tests have five metrics: Available Bandwidth, Capacity, Jitter, Latency and Packet Loss. In addition to each of the ThousandEyes test types, alerts also have metrics. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean?​
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
Maximum: The maximum value in the set of measurements, such as the response times of an HTTP Server test in a test round.
Minimum: The minimum value in the set of measurements, such as the response times of an HTTP Server test in a test round.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP Server test indicate the total number of HTTP Server alerts received in the reporting period.
Active Time: The amount of time an alert rule was active. (Alerts metrics only)
Inactive time: The amount of time an alert rule was inactive. (Alerts metrics only)
One Chart per Line: When checked, the widget will create a chart for each member of the setting specified in the Group By column. For example, if Group By is set to "Agent", then a chart will be created for each agent, rather than one chart graphing all of the lines.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Group By:
Single Line: Data from all sources and tests are aggregated together into a single line.
Test: Data from all sources and tests are aggregated together into a single line.
Agent: Data from all agents are given their own chart lines.
Continents: Data are aggregated by continent. A chart line is displayed for each continent that has data from at least one source.
Countries: Data are aggregated by country. A chart line is displayed for each country that has data from at least one source.
None: Data are not aggregated.
All: Group all the data as a single chart line.
Test Labels: Data from each test label is given their own chart lines.
Sources: Data from each source is given their own lines on chart.
Agent Labels: Data from each agent label is given their own chart lines.
Servers: Data aggregated based on servers. Each server has a dedicated chart line.
Visited Sites: Endpoint Data from each visited site is given their own chart lines.
Private Networks: Data from each private network is given their own lines on chart.
Users: Data is aggregated based on user, each user gets their own chart lines.
Platforms: Data from each platform Windows/Mac is given their own chart lines.
Connections: Data for each connection is given their own lines on chart.
Networks: Data aggregated based on networks, each network gets their own chart lines.
Domains: Data aggregated based on visited domain, each domain would have a dedicated chart line.
Endpoint Agent Labels: Data from each Endpoint Agent label gets its own line on the chart.
Device: Data from each device is given their own chart lines.
Device Types: Data from each type of device is given their own chart lines.
Interfaces: Data from each device interface is given their own chart lines.
Interface Types: Data from each device interface type is given their own chart lines.
Note: If the Group By field's setting is the same as the Source field type (e.g. Group By is "Test" and Source type is "Test", Group By is "Countries" and Source type is "Countries", or Group By is "Monitors" and the Source type is "Monitors"), the Source field takes precedence.
For example, if Group By is "Countries" and Source type is "Tests", then all selected tests will have their data grouped by all countries found from those tests' results. Each country will have its own graph. However, if Group By is "Countries" and Source type is "Countries", then only those countries selected in the Source selector will have their own graph.
Tests: Names of tests that will provide the data to the report. Based on your selection of Metric setting, the Tests menu will display only those tests that are relevant (e.g. if the Metric is Packet Loss, the Test menu displays Network tests and other tests that use an included Network test; if the metric is Availability, the Test menu displays a Web test, etc.).
Sources: Filter sources from which the data will be taken. The selections change based on which Metric is set, and will be one of the following:
Alert Rules: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of alert rules.
Agents: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agents.
Agent Labels: If the Metric is a Network, Web, DNS or Voice test or alert metric, a list of Cloud and Enterprise Agent labels (Built-in or Custom).
Tests: For any Metric, a list of tests.
Test Labels: For any Metric, a list of test labels (Built-in or Custom).
Monitors: If the Metric is a BGP test or alert, a list of ThousandEyes BGP monitors.
Example Time Series Widget
Below is an example of a configured time series widget and the resulting output.
1.
The above widget visualizes Maximum Packet Loss detected by an agent-to-server test. Data Source is configured to Cloud and Enterprise Agents.
2.
The data is aggregated by agent, resulting in each agent's data rendered on an indivudual chart line.
3.
“One Chart per Line” checkbox results in each line being rendered in a separate chart.
4.
Configured to visualize data from 1 of 189 available tests.
Stacked Bar Chart Widget
The image below shows an unconfigured stacked bar chart widget.
Stacked bar chart widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from Platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For a stacked bar chart widget, the metrics provided (Response Time, Total Fetch Time and Total Error Count) are composites of metrics found in an HTTP Server test. For example, Response Time consists of four distinct metrics: DNS resolution time, connect time, SSL time and wait time. Each of the four metrics are presented in a single stacked bar. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean?​
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive (Total Error Count only): The percentage of measurements with non-zero error counts. 
% zero (Total Error Count only): The percentage of measurements with error counts equal to zero.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Maximum: The maximum value in the set of measurements, such as the response times of an HTTP Server test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the response times of a HTTP Server test over the time period of the report.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Response Time" would indicate that the average value of the response time in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Response Time" would indicate that the value of 50 ms is the middle value in the range of all values of the response time in the reporting period.
Standard Deviation: The population standard deviation of a set of measurements, such as the response times, over the time period of the report.
Total (Total Error Count only): The total number of errors in the reporting period.
Axis: Arrange the data into bars by the following criteria, and orient the label(s) on the axis displayed :
All: Produces a single bar with all data.
Agent: Produces bars for each agent.
Continents: Produces bars for each continent/continental region (North America, Europe/EMEA, Asia/APAC, etc...).
Countries: Produces bars for each country.
Test: Produces bars for each test.
Test Labels: Each test label has its own bar.
Sources: Produces dedicated bars for each source.
Visited Sites: Each visited site has its own bar.
Private Networks: Each private network has its own bar.
User: Each user has its own bar.
Connection: Each connection gets a dedicated bar.
Network: Produces bars for each network.
Domain: Each visited domain has its own bar.
Location: Each location would have a dedicated bar.
Endpoint Agent Labels: A separate bar is produced for each Endpoint Agent label.
Endpoint Tests: Each Endpoint test has its own bar.
Devices: Each device is dedicated a bar on graph.
Interfaces: Device interfaces would have dedicated bars.
Device Types: Separate bars produced for each type of device.
Interface Types: Each interface type would have dedicated bars.
Either X-Axis or Y-Axis is displayed, based on the Orientation selected.
Orientation: The orientation of the bars--either horizontal or vertical. Selecting horizontal or vertical orientation sets the associated pull-down menu label to X-Axis or Y-Axis.
Sort By: For charts containing multiple bars, the Sort By setting will determine in what order the bars appear. That is, the value of the Sort By setting is applied to the value in the X-Axis/Y-Axis setting.
Default (Highest): Sort bars optimally, based on the settings for Metric and Show Comparison. The metric that is optimal for your settings is shown in parentheses.
Alphabetical: Sort bars by ascending alphabetical order.
Alphabetical (Reverse): Sort bars by ascending alphabetical order.
Highest: Sort bars by highest value first.
Lowest: Sort bars by lowest value first.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Limit To: When checked, the chart will display at most the number of groups you set in the selector. When more groups exist than are displayed, the Sort By order determines which rows are displayed.
Sources: Filter on names of tests or agents that will provide the data to the report. To filter by both tests and agents, click the + icon to the right of the pull-down menu.
Example Stacked Bar Chart Widget
Below is an example of a configured stacked bar chart widget and the resulting output.
1.
The configured widget visualizes mean Response Time for HTTP Server tests based on Cloud and Enterprise Agents.
2.
Graph is configured to be oriented to extend from left to right with Y axis as Servers sorted alphabetically.
3.
This widget is visualizing 4 out of 149 available HTTP server tests.
Grouped Bar Chart Widget
The image below shows an unconfigured grouped bar chart widget.
Grouped bar chart widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from Platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For example, agent-to-server tests have five metrics: Available Bandwidth, Capacity, Jitter, Latency and Packet Loss. In addition to each of the ThousandEyes test types, alerts also have metrics. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean?​
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Maximum: The maximum value in the set of measurements, such as the response times of an HTTP Server test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the response times of a HTTP Server test over the time period of the report.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Standard Deviation: The population standard deviation of a set of measurements, such as the response times, over the time period of the report.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP Server test indicate the total number of HTTP Server alerts received in the reporting period.
Axis: Arrange the data into bars by the following criteria, and orient the label(s) on the axis displayed :
All: Produces a single bar with all data.
Source: Produces bars for each source of data (test or agent).
Continents: Produces bars for each continent/continental region (North America, Europe/EMEA, Asia/APAC, etc...).
Countries: Produces bars for each country.
Test: Produces bars for each test.
Test Labels: Each test label has its own bar.
Sources: Produces dedicated bars for each source.
Visited Sites: Each visited site has its own bar.
Private Networks: Each private network has its own bar.
User: Each user has its own bar.
Connection: Each connection gets a dedicated bar.
Network: Produces bars for each network.
Domain: Each visited domain has its own bar.
Location: Each location would have a dedicated bar.
Endpoint Agent Labels: A separate bar is produced for each Endpoint Agent label.
Endpoint Tests: Each Endpoint test has its own bar.
Devices: Each device is dedicated a bar on graph.
Interfaces: Device interfaces would have dedicated bars.
Device Types: Separate bars produced for each type of device.
Interface Types: Each interface type would have dedicated bars.
Either X-Axis or Y-Axis is displayed, based on the Orientation selected.
Orientation: The orientation of the bars--either horizontal or vertical. Selecting horizontal or vertical orientation sets the associated pull-down menu label to X-Axis or Y-Axis.
Group By: One or more sets of bars are produced for each of the values in the Axis setting, based on the value of the Group By setting. The available settings will be among the following:
All: All data aggregated into one bar
Test: Data from all sources and tests are aggregated together into a single line.
Source: Data from all tests or agents are given their own bars.
Continents: Data are aggregated by continent. A chart line is displayed for each continent that has data from at least one source.
Countries: Data are aggregated by country. A chart line is displayed for each country that has data from at least one source.
Test Labels: Data from each test label is aggregated into a single line.
Sources: Data from each source is aggregated into a single line.
Agent Labels: Data from each agent label is aggregated into a single line.
Servers: Data aggregated based on servers in a single line.
Visited Sites: Endpoint Data from each visited site is aggregated into a single line.
Private Networks: Data from each private network is aggregated into a single line.
Users: Data is aggregated based on user into a single line.
Platforms: Data from each platform Windows/Mac is aggregated into a single line.
Connections: Data for each connection is aggregated into a single line.
Networks: Data aggregated based on networks into a single line.
Domains: Data aggregated based on visited domain into a single line.
Endpoint Agent Labels: Data from each Endpoint Agent label is aggregated into a single line.
Device: Data from each device is aggregated into a single line. 
Device Types: Data from each type of device is aggregated into a single line.
Interfaces: Data from each device interface is aggregated into a single line.
Interface Types: Data from each device interface type is aggregated into a single line.
Sort By: For charts containing multiple bars, the Sort By setting will determine in what order the bars appear. That is, the value of the Sort By setting is applied to the value in the X-Axis/Y-Axis setting.
Default: Sort bars optimally, based on the settings for Metric and Show Comparison. The metric that is optimal for your settings is shown in parentheses.
Alphabetical: Sort bars by ascending alphabetical order.
Alphabetical (Reverse): Sort bars by ascending alphabetical order.
Highest: Sort bars by highest value first.
Lowest: Sort bars by lowest value first.
Fixed Time Span: When checked, a date selector will appear, allowing selection of a range of days different than the one specified for the entire report. The widget will display data in that range.
Limit To: When checked, the chart will display at most the number of groups you set in the selector. When more groups exist than are displayed, the Sort By order determines which rows are displayed.
Sources: Filter on names of tests or agents that will provide the data to the report. To filter by both tests and agents, click the + icon to the right of the pull-down menu.
Example Grouped Bar Chart Widget
Below is an example of a configured grouped bar chart widget and the resulting output.
1.
The chart is configured to visualize Mean Receive Time from HTTP Server tests based on Cloud and Enterprise Agents.
2.
Graph is configured to extend horizontally with Servers as Y axis grouped by agent labels and sorted in a descending order.
3.
Widget is configured to visualize 5 out of 149 tests.
Pie Chart Widget
The image below shows an unconfigured pie chart widget.
Pie chart widgets have the following settings:
Data Source: The data source indicates which platform service will be referenced within the widget. Current options include:
Alerts: Data is obtained from Platform alerts
Cloud and Enterprise Agents: Data is obtained from scheduled tests performed by Cloud and Enterprise Agents
Devices: Data is obtained from device-layer reporting
Endpoint Agents: Data is obtained from scheduled tests and monitored domain metrics
Routing: Data is obtained from BGP tests
Metric: Each type of ThousandEyes test has its own metrics. For a pie chart widget, the metrics provided (Response Time, Total Error Count and Total Fetch Time) are composites of metrics found in an HTTP server test. For example, Response Time consists of four distinct metrics: DNS resolution time, connect time, SSL time and wait time. Each of the four metrics are presented in a single pie chart. For more information on ThousandEyes metrics, see ThousandEyes Metrics: What Do Your Results Mean?​
Measure: A statistical measurement. Measure types available depend on the Metric setting, and will be one or more of the following:
% positive: The percentage of measurements greater than zero. For example, the percentage of time when a Network alert was active.
_% zero: **_The percentage of measurements equal to zero. For example, the percentage of time when a Network alert was active.
nth Percentile: The value of the metric that contains n% of the measurements. When "nth Percentile" is selected, a text box will appear, allowing you to specify an integer for the percentile value from 1 to 99. 98% is the default. For example, a 98th Percentile whose value is 500 ms for a Metric of "Response Time" would indicate that 98% of the measurements of the response time were between 0 and 500 ms.
Maximum: The maximum value in the set of measurements, such as the response times of an HTTP Server test over the time period of the report.
Minimum: The minimum value in the set of measurements, such as the response times of a HTTP Server test over the time period of the report.
Mean: The value of the arithmetic mean (i.e. average) of the measurements. For example, a Mean of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the average value of the latency in the reporting period was 50 ms.
Median: The value of the median measurement. For example, a Median of 50 ms for a Metric of "Latency" for one or more Network tests would indicate that the value of 50 ms is the middle value in the range of all values of the latency in the reporting period.
Standard Deviation: The population standard deviation of a set of measurements, such as the response times, over the time period of the report.
Total: The total number of measurements. For example, a Metric set to "Alerts" and Tests set to a HTTP Server test indicate the total number of HTTP Server alerts received in the reporting period.
Group By: One or more pie charts are produced based on the value of the Group By setting. The available settings will be among the following:
All: All data aggregated into one pie chart.
Agent: Data from all agents are aggregated into a single pie chart.
Continents: Data are aggregated by continent. A pie chart is displayed for each continent that has data from at least one test.
Countries: Data are aggregated by country. A pie chart is displayed for each country that has data from at least one test.
Test: Data from all tests are aggregated into a single pie chart.
All: Group all the data as a single chart.
Test Labels: Data from all associated test labels are aggregated in a single pie chart.
Sources: Data from each source is given their own pie charts.
Agent Labels: Data from each agent label is given its own pie chart.
Servers: Data aggregated based on servers. Each server would have a dedicated pie chart.
Visited Sites: Endpoint Data from each visited site is given its own pie chart.
Private Networks: Data from each private network is given its own pie chart.
Users: Data is aggregated based on user, each user gets their own pie chart.
Platforms: Data from each platform Windows/Mac is given its own pie chart.
Connections: Data for each connection is given its own pie chart.
Networks: Data aggregated based on networks, each network gets its own pie chart.
Domains: Data aggregated based on visited domain, each domain would have a dedicated pie chart.
Endpoint Agent Labels: Data from each Endpoint Agent label gets its own pie chart.
Device: Data from each device is given its own pie chart. 
Device Types: Data from each type of device is given its own pie chart.
Interfaces: Data from each device interface is given its own pie chart.
Interface Types: Data from each device interface type is given its own pie chart.