Changelog
Starting April, 2021, the Google Chrome and Microsoft Edge browser extensions are installed by default in new installations of Endpoint Agent on Windows endpoints. Users can opt-out of the installation as part of the Endpoint Agent installer process.
If you opt not to install the extensions as part of the Endpoint Agent installer process, you can still install them separately. See Install the Browser Extension.
The ThousandEyes Endpoint Agent is now able to identify the presence of Zscaler Internet Access (ZIA) on customer machines allowing us to gather metrics and performance measurements for traffic transiting the Zscaler network. Metrics and measurements are displayed in the UI in the same way as other supported VPN providers. Some ZIA deployment models may not be fully supported. For more information see Endpoint Agent VPN Support.
ThousandEyes has introduced a new image for its Docker Enterprise Agents that attaches an anonymous Docker volume to each container running the Enterprise Agent. This change supports a future enhancement that will improve the consistency and performance of browser-based tests.
The endpoint scheduled test table now displays a dash rather than 0% loss if the loss is in fact null, which may happen if ICMP measurements could not be completed.
The ThousandEyes Endpoint API has been extended to allow existing agent labels to be updated.
The API /endpoint-agents now correctly respects the "deleted" flag when returning a list of agents. By default this flag is false - only non-deleted agents are returned.
The Endpoint Agent basic service set identifiers (BSSID) table now shows a list of all of the BSSIDs detected in a test round.
The location of the Endpoint Agent is no longer updated if insufficient WiFi data is obtained from the end user machine, to avoid occasional "flapping" between agent locations that occurred due to operating system inconsistencies in obtaining the WiFi data used for obtaining geolocation data.
In cases where the speed score cannot be calculated due to an error gathering data for the page, the experience score is now set to 0 rather than -.
The default widget time on reports has been updated from 7 days to 1 day. This value can still manually be changed by the customer at the report level or the individual widget level.
Effective March 30, ThousandEyes will cease support for Internet Explorer 11 for https://app.thousandeyes.com. Support for all other browsers remains unchanged.
Fixed an improper handling of an aborted request that could result in an occasional failure to display an Endpoint Agent Path Visualisation.
An issue was found where creating an Endpoint agent scheduled test via the API could throw a 500 Internal Server Error. This has been resolved.
An issue occurred where our third-party provider of geolocation data was wrongly assigning an IP address to a location in the UK rather than in New York City, USA. This is now resolved.
An edge case was found where, when an Endpoint alert rule was applied to a scheduled test, the test would show the assigned rule, but the alert rule would show 0 assigned tests. This issue has been resolved.
API endpoint /v6/endpoint-data/user-sessions no longer returns 500 when only the "from" field is specified. In this case, the end date of the query will default to the current time.
API endpoint /v6/endpoint-data/network-topology no longer returns 500 when specifying only the "from" field is specified. In this case, the end date of the query will default to the current time.
Previously, unresolved VPN overlay targets were displayed on the path visualization as 0.0.0.0, which was misleading. This has been corrected, and they are no longer displayed.
An issue was found where a deleted Endpoint Pulse Agent was still being returned in API calls. This has been resolved.
Previously, an issue occurred where a combination of filters was interpreted as OR rather than AND. The path visualisation agent filter now correctly filters the list of agents.
Previously, it was possible to see different colours when clicking a group to expand it versus when you applied the equivalent filter manually. The path visualisation now shows consistent colours for groups.
In a small number of cases, test data was not collected as scheduled tests data points were discarded if the tests couldn’t finish within their expected time bounds. Data points are no longer discarded in this case.
Fixed an issue where the interactive Endpoint Agent Windows installer could fail installing a COM component and return an error "There is a problem with this Windows installer package."
Fixed an issue where a handful of no longer valid BGP alerts were incorrectly being included in reporting and dashboarding widgets due to an incorrect clear time on the alerts.
An issue was found where enterprise agents running shared tests were not showing up as a filter option in the shared to account group while using dashboards and reports. This has been resolved.
An issue was found where the hard render limits put in place for report and dashboard widgets were not transparent to users in our multi-metric table widget. Previously, if a multi-metric table request was too large, we would simply say "No Data." We have now added a tooltip that explains that the data cannot be rendered because the request is too large.
Fixed an issue that prevented test labels from being used in reports and dashboards in relation to our BGP hard render limits. A user can now select a test label and the hard render limit calculation will correctly apply. For more information on our render limits, see Working with Reports.
Fixed an issue that occurred when a user tried to deselect a filter selection in a dashboard or report widget and the filter inadvertently closed instead of letting the user deselect multiple options at a time.
Fixed an issue where a small number of users with the correct edit permissions were not able to edit existing alert rules.
As of March 15, 2021, the DNS+ test type has been removed from the ThousandEyes product. DNS+ tests can no longer be created, and any existing DNS+ tests and snapshots are in the process of being deleted. For more information, contact your account team or ThousandEyes support.
An Endpoint Agent IP address was wrongly identified as being located in the United Kingdom, rather than in Japan, by our geolocation data provider. This issue has been resolved with our provider, and the correct data should be present in the product from March 19, 2021.
The ThousandEyes reporting and dashboard platform is moving to a new backend data store to provide a faster and more responsive customer experience. The first data sources moving to this new data store are Endpoint Agent sources for Web - HTTP server, Network - agent-to-server, and network topology. The hard limits that have been applied to these data sources will gradually be removed over time as we move towards a 90-day retention period in our new data store.
Starting today, there will be no hard limits applied to data requests from January 23rd, 2021 onward. Any dashboard or reporting requests for data before January 23rd, 2021, will be met with the same hard limits currently in place for endpoint data. For more information on these hard limits, see the product documentation.
As of this release, customers with Cisco Catalyst 9300 switches running IOS-XE 17.3.3 can deploy our Enterprise Agent on the Catalyst 9300 natively - that is, without using an SSD.
As part of this effort, we've also redesigned the Add New Enterprise Agent modal:
Cisco deployment types are now shown in a separate Cisco Application Hosting tab.
The account group token now appears at the top of the tab, to make it easier to find and copy during agent installation.
As previously announced, ThousandEyes has ended support for classic transaction tests as of March 1st, 2021. Classic transactions tests can no longer be created, enabled, or run as instant tests.
Classic test data will remain available for test views, API requests, and reports in accordance with our data retention policies.
Effective March 30, 2021, ThousandEyes will cease support for Internet Explorer 11 for https://app.thousandeyes.com. Support for all other browsers remains unchanged.
In v7 of the Dashboards API and Reports API, the JSON that is returned now refers to all dataSource, direction, filters, metric, measure, and metricGroup values using an all-caps, snake-cased literal, rather than the display name shown in the ThousandEyes platform's UI. The API will continue to accept display names in JSON when posting, but will use enum names in the JSON that is returned from requests.
This change is only for v7 of the API.
Note: v7 of the ThousandEyes API is in preview status, and is subject to change.
For example, before this change, the response JSON might read as follows:
"dataSource": "Cloud & Enterprise Agents","metricGroup": "Network - Agent to Agent","direction": "Both Directions","metric": "Packet Loss",
After this change, the same JSON response will read as follows:
"dataSource": "CLOUD_AND_ENTERPRISE_AGENTS","metricGroup": "AGENT_TO_AGENT","direction": "BIDIRECTIONAL","metric": "ONE_WAY_NET_LOSS_BIDIRECTIONAL",
In the past, the default BGP alert rule was automatically selected and attached to higher-level network, web, DNS, and voice tests when they were created. With this release, the default BGP alert rule is no longer automatically applied to the following test types:
Network - Agent-to-server
Network - Agent-to-agent
DNS server
Web - HTTP server
Web - Page load
Web - Transaction
FTP - Server
Voice - SIP server
Voice - RTP stream
This change does not affect any existing tests that have this alert rule.
Note: This change applies to any BGP alert rules that are designated in your system as default. To see which BGP alert rules you have designated as default, go to Alerts > Alert Rules > BGP Routing and see the selections in the Default column.
For new tests of the above types, you can still select the default BGP alert rule manually and apply it to these tests if you wish. For any new BGP tests you create, the default BGP alert rule is still automatically applied.
For cases where a machine has multiple users, the Endpoint Agent's Agent Details list now displays an icon next to each user name, to show the status of the browser extension for this user.
Fixes around deleting an Endpoint Agent:
Deleted Endpoint Agents now only appear in the Agent Labels filter options dropdown list if they have been previously selected in the label. A deleted agent can be recovered for a seven-day period after deletion. If a deleted agent was included in a label and is within its seven-day recovery period, it may appear in the Agent Labels list.
When you perform a bulk-delete operation of Endpoint Agents, the list of agents is now updated correctly. Previously, in some cases deleted agents could still be shown, or search results were incorrectly filtered.
Endpoint Agents that were deleted more than one week ago are no longer displayed.
An issue was fixed in which some BGP alert rules were not triggering when an unexpected covered prefix was advertised, despite the alert rule being set up to trigger for this condition.
An erroneous error message was presented when a user generated a DNS server sharelink from the Network Overview layer of a DNS server test. Although the sharelink captured the relevant test data, the error message was misleading. This issue has been fixed.
An issue was fixed in which the colors on the color grid widget were not accurately reflecting the scale selected by the user.
Certain strings in report and dashboard widgets were being incorrectly and inconsistently truncated. This issue has been fixed.
An intermittent issue was fixed in which an embedded alert grid widget was not redirecting users to the the correct URL when they clicked an alert.
For Endpoint Agents, the path visualization for local networks now correctly displays the **Avg. Response** metric on hops and the **Delay** metric on links.
The Agent Settings, Test Settings, and Agent Labels sections of the ThousandEyes application for Endpoint Agents have undergone a substantial redesign. The following sections outline the major changes that have been made.
Agent specific settings are now displayed in a modal, rather than inline:
Added a list of labels applied to the agent.
Added a timeline of the number of tests allocated to the agent on a Time Series graph.
Added a list of all scheduled tests associated with the agent.
Hid the Agent's details to streamline the UI.
Users can now add filters for any of the device attributes (including username, or users who are members of a label etc).
Added a Last Modified column to the table.
Agent usernames are now displayed beneath the agent name.
Agent labels have a new, condensed, icon. Hovering over the icon will display a list of the labels.
Individual test settings are now opened in a modal, rather than in-line.
The following new columns have been added to the table:
Last Modified: Last time this test was edited.
Assigned Agents (24h): The number of agents assigned to the test in the last 24 hours.
The enabled/disabled option is now a switch.
Tests can now be assigned to All Agents, one or more labels, or one or more specific agents. Additional filters have been added to support this feature:
You can now filter by Assignment Type, Agent Label, and by Agent.
Updated the Time Series graph that shows the number of agents assigned and running the test.
Added a list of all agents assigned and running the test.
The Show/Hide Details option now opens/closes an additional panel that includes the Last Modified, Labels and Views Enabled for this Test information.
The Add New Label form is now a side panel, rather than a floating modal.
Agent labels are now displayed as tags rather than circles.
The 24 hour time series now includes:
All agents matching the label's definition.
The agents that are available and also have not exceeded the number of tests running.
From February 23 2021, the Endpoint data API will support 30 days of retention. If you require more than 30 days, our Reports and Dashboards have a data retention of 90 days. For more information, see the Reports and Dashboards documentation.
New Cloud Agents have been added to the following locations:
Quebec City, Canada (IPv6)
Cape Town, South Africa (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
Previously, a 404 error was presented when visiting a snapshot link while it was still being generated. This has now been updated to a progress indicator so that users are aware that the snapshot is still being generated.
In some circumstances, double counting of Endpoint Agents occurred when an Endpoint Agent was transferred between users or account groups. The calculation has been updated to reduce the chance of overage notifications when the effective number of agents is still below the organization's subscription amount.
An issue was found where the scale of the color grid widget was not resetting to auto after clearing the field of any values. This has been resolved.
In rare cases, the CSV download option was not working on a subset of select reports. This has been fixed.
An issue was found where the ability to show overall mean on a time series widget was not selectable during configuration and only selectable after a widget was saved. This has been corrected.
An issue was found with the timeline where the y-axis was not showing the correct scale when updating the selected metric. This has been fixed.
An issue was found where multiple IP addresses appeared when specifying a static IPv4 address. This has been resolved.
An issue was found where agent updates would fail if NTLM/Kerberos authenticated proxies were being used. This has been fixed.
As of February 15th, 2021, ThousandEyes has completed our infrastructure transition to Amazon Web Services. We have also made substantial updates to the Firewall Configuration for Enterprise Agents article, including the new ThousandEyes IP addresses that can be used by customers for their firewall rules or access control lists.
A typo was found in the ThousandEyes Infrastructure Changes list of IP addresses to use in allowing connections to api.thousandeyes.com. The document has now been updated to reflect the correct IP address (13.248.200.34).
The ThousandEyes Recorder now supports exporting transaction tests and synchronizing credentials to the ThousandEyes platform. For more information, see ThousandEyes Recorder.
Endpoint Agent VPN support for Palo Alto's GlobalProtect VPN is now available to all customers. For more information, see Endpoint Agent VPN Support.
An issue was found where cleared alerts were still showing in the alert list, despite the error condition no longer being met. This was caused by the addition of several BGP monitors and the associated missing data collection of these monitors, and has now been resolved.
An issue was found where the ability to add a custom webhook payload was visible for non-supported alert types. This functionality is now only visible within the supported Cloud and Enterprise Agent alert webhooks.
An issue was found where a timeseries widget showed no data when it was included in a downloaded report PDF. This has been fixed.
Multi-service views allow ThousandEyes users to build a more comprehensive view of their environment by combining multiple test views into one multi-service view. For more information, see Multi-Service Views.
The SNMPv3 authentication protocol options for device credentials have been expanded to include support for RFC 7860 protocols:
In October 2020, ThousandEyes migrated backend BGP services. Some BGP alerts that were active during this migration failed to resolve.
Active BGP alerts created on or before 2020-10-20 will be resolved by the ThousandEyes operations team. Resolved alerts will still appear within an account group's alert history. If the post resolution state of a BGP test triggers an assigned alert rule, a new alert will be created.
Tests can now be created, updated, and deleted with the sourceIPAddress attribute for Endpoint Agent interface selection via the API. The sourceIPAddress attribute can be specified in the "Agents" list to define a particular sourceIPAddress to be used.
New Cloud Agents have been added to the following locations:
Cape Town, South Africa (AWS af-south-1) (IPv4)
Spokane, WA (IPv4 and IPv6)
Tel Aviv, Israel (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
Two minor enhancements have been made to how the installation status of an Endpoint Agent browser extension is displayed:
Previously, only one extension was considered when returning filter results. Now, all extensions are checked when filtering by browser extension status.
The Not installed status now denotes that at least one supported browser does not have a ThousandEyes extension installed (this includes instances where no supported browsers are installed).
The headers for some page elements in the Endpoint Agent Browser Sessions > Waterfall view were found to be missing, and have now been restored.
An issue was found where the UI hint text stated that Endpoint Agents could be searched for on the Agent Settings page by both the agent name and the hostname. This was incorrect, as only the agent name was considered by the search function. This has been fixed, and users can now search by either agent name or hostname as expected.
A display issue that caused some Endpoint Agent path visualization nodes to be displayed backwards (from right to left) has been resolved.
An issue was found where the minimum path MTU in the path visualization agent tooltip was inaccurately shown as "-1". This has been resolved.
Endpoint Agent users can opt-in to install the Google Chrome and Microsoft Edge browser extensions alongside the Endpoint Agent, either:
If you opt not to install the extensions as part of the Endpoint Agent installer process, you can still install them separately. See Install the Browser Extension.
From April 2021, the installation of the Google Chrome and Microsoft Edge extensions will be automatic and will no longer be opt-in.
On the Feature Selection page of the installer wizard, open the drop-down menu for the desired extension, and select the relevant option.
Users can install one or both of the extensions as necessary.
Once you have configured the extensions, click Next to continue the installation wizard.
To install the extensions via the command-line, add the relevant flags shown in the examples below:
Google Chrome extension:
msiexec.exe /i <path_to_msi> /quiet /norestart /qn ADDLOCAL="ChromeExtension"Microsoft Edge extension:
msiexec.exe /i <path_to_msi> /quiet /norestart /qn ADDLOCAL="EdgeExtension"Both extensions:
msiexec.exe /i <path_to_msi> /quiet /norestart /qn ADDLOCAL="ChromeExtension,EdgeExtension"
An update has been made to the snapshot sharing modal. To generate a URL link for the snapshot, click the Share button:
A URL link for the snapshot will then be generated:
New IPv6 Cloud Agents have been added to the following locations:
Ottawa, Canada
Kuala Lumpur, Malaysia
Cheyenne, WY
Nagoya, Japan
In addition, the Tokyo, Japan IPv6 Cloud Agent has a new provider (NTT).
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
The Endpoint Agent error messages shown when the machine has connectivity issues or the wrong content-length header have been improved, and split into two more specific error messages:
“Content-Length header is invalid or has been corrupted”.
"The user’s internet connectivity was interrupted”.
The timezone is now included in downloaded report PDFs to avoid timeline confusion.
An error occurred where the clicking on Show only this agent for entire view in an Endpoint Agent scheduled test table would not activate the Details for agent state when switching to the Map tab. This has been fixed.
An error was found where the Endpoint Agent would stop listening for the response to ping messages for a few milliseconds before the ICMP response was received. This issue has been resolved.
Previously, targets without RDNS entries would incorrectly be resolved to their authoritative server's name. These targets are now only displayed as IP addresses.
An issue was fixed where the DOM Load Time metric for transaction tests was incidentally showing pages with 0 data points.
An issue occurred where incorrect color coding was used in agent to agent tests, resulting in available metrics appearing to be unavailable. This has been resolved.
On March 15th, 2021, the DNS+ test type will be removed from the ThousandEyes product.
Previously, DNS+ tests, including DNS+ server latency tests and DNS+ domain tests, leveraged open DNS resolvers to gather DNS record availability information and nameserver performance. However, due to the transient nature of open resolvers on the internet, maintaining and discovering a global list of resolvers has become operationally difficult.
DNS server tests can be used to test against public and common ISP resolvers using our Cloud Agent vantage points around the world. Used in conjunction with alert rules for the Mappings metric, DNS server tests can monitor DNS servers for use cases such as cache poisoning.
Other DNS test types, including DNS trace tests and DNSSEC tests will also remain supported.
After March 15th, customers will no longer be able to create new DNS+ tests, and any existing DNS+ tests and snapshots will be deleted. For more information, contact your account team or ThousandEyes support.
Page DOM Load Time and Page Load Time are now selectable widget metrics in reports and dashboards for the transaction metric type. A user can group their data by the individual pages identified in their transaction test.
Previously, queries to https://api.thousandeyes.com/v7/endpoint-data/tests/net/metrics/ returned 100% loss when ICMP measurements were blocked. This has been updated - queries now return the ErrorDetails field.
To improve user experience when there are a large number of white nodes in an Endpoint Agent path visualization, these white nodes will now be grouped together when there are three or more consecutively.
Previously, if there was a DNS failure when resolving the target of a scheduled test, no network scheduled test datapoints would be uploaded to the backend. In this case the agent would appear as if it didn't participate at all running scheduled tests at those rounds. Failed scheduled tests ping and pathtrace datapoints are now generated if the name resolution to the target failed.
A display formatting error in the Endpointn Agent Browser Sessions network table was found that made the values inconsistent with those shown in the path visualization. This has been resolved.
An issue that caused the loading spinner icon to not disappear when an Endpoint Agent page request completed has been fixed.
The screen placement of the Agent Filter dropdown menu prevented some agents from being selectable. This issue has been resolved.
An issue that caused ICMP blocked traffic to trigger browser session alerts on packet loss has been resolved.
An issue that caused scheduled snapshots with the Number Card widget to be displayed incorrectly has been fixed.
An issue was found where throughput metrics were being collected for agent-to-agent tests, but were not a selectable metric on the timeline. This has been resolved.
In cases where an agent used a proxy but was told to go directly to the target by the PAC file, the Target IP address was incorrectly displayed as the proxy IP address. This has been resolved.
In rare circumstances, a BGP alert rule would still show as triggered even though the rule had been deleted. This has been resolved.
In rare instances, an alert was fired after 1 round when the associated alert rule specified multiple rounds were required to fire the alert. This error has been corrected.
Please review the features below that we are retiring on March 1st, 2021.
ThousandEyes will end support for classic transaction tests after March 1st, 2021. Classic test data will remain available for test views, API requests, and reports in accordance with our data retention policies. Customers may use saved events to retain test data beyond our standard retention timelines.
For more information on migrating classic transaction tests, see Transaction Test Migration Workflow.
If you have any questions, please reach out to ThousandEyes support through in-app chat, available 24 hours a day.
Three new metrics have been added for the Device layer to improve topology highlighting and surfacing of device-based issues. The new metrics are:
Interfaces with State Changes
Errors and Discards
CPU Utilization
As part of this update, metric selection above the timeline is now decoupled from highlighting options in the Device topology views (similar to standard test views).
Proxy Loss, Proxy Jitter, and Proxy Latency have been added as alert conditions for agent to server alerts.
Proxy Loss, Proxy Jitter, and Proxy Latency have been added to the ThousandEyes API under the /v6/net/metrics/{testId} endpoint.
A bug was found that prevented the bulk transfer of Endpoint Agent ownership from one account group to another. This has been resolved.
A bug was found that resulted in an infinite page load spinning icon when opening the Endpoint Agent Local Networks view. This has been resolved.
On newly installed Endpoint Agents, the presence of the Cisco AnyConnect VPN client was not detected after startup. This was due to a configuration error, and has been resolved.
A bug was found where Endpoint Agent tests were run but the results were not submitted. This was caused by how timeouts were handled across redirects, and has been resolved.
An issue was found where the Number Card report widget would not save configuration changes. This has been corrected.
An issue that resulted in Multi-Metric Table widgets incorrectly showing the 98th percentile value regardless of how the widget was configured has been fixed.
An issue was found where the Response Code metric was showing up on active alerts in the Metrics at Alert Start column, even though they weren't part of the triggered error condition. This has been corrected.
A path visualization issue resulted in the proxy icon not displaying properly when there was a loop at the proxy. This has been resolved.
A database replication issue caused device discovery on some devices to fail. This has been fixed.
An issue was found where, in some cases when an HTTP redirect was involved, the certificate chain was not being presented in the HTTP server response details. This has been resolved.
An NTP issue prevented customers from deploying ThousandEyes agents using the new appliance type based on Ubuntu 18.04 LTS. This issue has been resolved.
As previously announced, ThousandEyes is transitioning its infrastructure to Amazon Web Services. ThousandEyes customers may have access control lists (ACLs), firewall rules, or other configurations (for example, /etc/hosts files with hard-coded IP addresses) that permit Enterprise Agents, Endpoint Agents, or other resources to communicate with the ThousandEyes infrastructure. These configurations must be updated with new IP addresses by November 15th, 2020. For instructions, see the article ThousandEyes Infrastructure Changes.
If you have questions or concerns, contact ThousandEyes Customer Engineering.
The Proxy Loss, Proxy Latency, and Proxy Jitter metrics are now available for view in dashboards and reports.
In addition, users can now see additional proxy details such as Proxy Name, Proxy IP, where the proxy setting is applied, and the type of proxy in the HTTP Server view.
The ThousandEyes Raspberry Pi installation image has been updated to support the 8GB version of the device.
The ThousandEyes virtual appliance installation image has been updated to use Ubuntu Bionic 18.04.5 LTS as the base operating system. All new virtual appliance installs will run using Ubuntu Bionic.
A new IPv6 Cloud Agent has been added to Indore, India. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
Widgets can now be removed from a report or dashboard by dragging them directly into a deletion zone (i.e., a trash can). This action can be undone immediately after deletion.
An alerting logic issue prevented BGP alerts from firing correctly, as setting the trigger threshold to 100% of monitors was detecting either IPv4 monitors or IPv6 monitors only, rather than the combined total. This has been corrected.
The Color Grid widget in reports and dashboards was sometimes displaying the wrong color based on the scale provided. This has been resolved.
General HTTP tests were not offering network alerts even if the setting to collect network measurements was on. This has been corrected.
A broken “Show Traces using this VPN" link in Endpoint Agent network tests has been fixed.
An issue prevented newly created Endpoint Agent test labels from showing up in the Endpoint Agent test list, and made them unavailable for searches. This has been resolved.
In instances where no data was collected when looking at Endpoint Agent wireless data, the data loading icon would not disappear. This has been resolved, and the correct message that no data was found is displayed.
An issue was found where clicking the Show Only This Agent link while interacting with the path visualization would not display pagination correctly. This has been corrected.
The API response format for web layer data requests was inadvertently changed in a previous release. The previous documented response format has been restored.
An issue was found where customers were unable to install Enterprise Agents in a VMware ESXi environment due to an incompatibility in the compression algorithm used. This is now resolved, and customers can install as expected.
ThousandEyes has updated the reports and dashboards user interface, widget icons, and workflow to substantially improve user experience, and ensure that widget addition and configuration is as streamlined as possible:
Widgets can now be added by clicking the + Add Widget button to open the Add a Widget panel, and then either selecting a widget to configure, or by dragging it to the desired location in the report or dashboard.
The Add a Widget side panel is now movable and minimizable, allowing users to review how the added widget looks before saving.
Changes to a widget can be previewed before saving. Clicking Cancel will revert the widget to its pre-configuration state, while clicking Save will confirm the new configuration.
As part of this update, the Manage Widgets section has been removed.
For more information on working with reports and dashboards, see:
Internet Insights customers can now add widgets to reports and dashboards to leverage Internet Insights network outage metrics. The network outage metrics provided are:
Affected Tests: Test data within your organization that is affected by outages.
Interfaces: Interface data affected by outages.
Locations: Location data affected by outages.
Outages: Overall outage data.
Widgets built on Internet Insights metrics can apply the following filter conditions: Catalog Provider, Outage Scope, and Network; Interface Location and Interface IP Address; Affected Test and Affected Domain; and Server Location, Server Prefix, and Server Network.
To add a widget with Internet Insights metrics:
In Reports or Dashboards, click + Add Widget and select a supported widget.
Select Internet Insights as the datasource.
Select Network Outages as the category.
Select a metric and measure (and filters if desired).
Internet Insights metrics are not available for use with the Stacked widget types (Stacked Bar, Stacked Area, and Pie).
A new pre-built dashboard that captures weekly and monthly outage trends has been added for Internet Insights customers. The dashboard, called Internet Insights Built-In, also provides an up-to-date view of the most impacted tests, locations, and providers.
The default dashboard can be duplicated and used as a starting point for building custom dashboards.
The Endpoint Agent now integrates with the Pulse Secure VPN, providing end-to-end visibility of network nodes and metrics for traffic that traverses the network. When present, the client will populate the VPN Vendor attribute visible in Endpoint Agent views and filters.
Device discoveries now report devices that failed discovery due to a lack of working credentials. The Edit Device modal has also been updated to show the used credentials on the device, and provide users with easy access to new credential creation:
A hard limit of 700 (for example, 50 tests over 14 days, or 100 tests over 7 days) has been added to improve performance when a report or dashboard widget is created with a large BGP data set (either due to no applied filters or too large of a time span). Users are now asked to either apply a BGP test or monitor filter, or to reduce the time span in order to render the data, if it would otherwise exceed the hard limit.
The Internet Insights alert rules functionality has been updated for when both Catalog Providers and Affected Tests are set to Any. Previously, this configuration would only trigger if a customer test was impacted by an outage. The configuration has now been updated to trigger if a subscribed provider is impacted, in addition to if a customer test is affected by an outage in a subscribed provider.
To alert on outages affecting only customer tests (including in providers the customer is not subscribed to), customers should set Affected Tests to Specific, and select all tests, or the specific set of tests you want the rule to match.
This change has been made to all existing alert rules.
In order to simplify test selection in Cloud and Enterprise Agent views, saved events have been removed from the test selector. Saved events can be accessed from the Sharing > Saved Events page in the main menu.
An issue was found where path trace data was not appearing in Endpoint Agent sharelinks. This has been resolved.
You can now gather network data and path-visualization data about proxy servers.
In the past, if your target was behind a proxy, your ThousandEyes tests would not collect network data. Workarounds existed (adding the target to the proxy's bypass list, or creating separate agent-to-server tests to the proxy), but these were cumbersome to configure. And with the popularity of cloud proxy solutions such as Zscaler, Netskope, and Palo Alto Networks, you may want to understand network health to the cloud proxy.
With the ability to run network tests to the proxy, you can more easily correlate data between the application and network layers. The new ThousandEyes proxy capabilities allow you to see
Proxy loss
Proxy latency
Proxy jitter
A visualization of the network path to the proxy
To explore the new proxy metrics:
Go to Cloud & Enterprise Agents > Test Settings.
Select or create an HTTP, page load, or transaction test.
On the Advanced Settings tab, find the Proxy Settings section.
Select Perform network measurements to the proxy.
Several improvements have been made to how Endpoint VPN data is visualized:
VPN loss and VPN latency metrics have been added to the Scheduled Tests, Browser Sessions, and Local Networks views.
The following filters have been added to Endpoint Agent Settings and Endpoint Agent labels:
VPN Vendor: The VPN vendor.
VPN Gateway IP address: The public IP Address of the VPN gateway/server.
VPN Client Address: The private IP via which clients route packets to the VPN tunnel.
VPN Client Network: The private network that the VPN client belongs to.
The old VPN Address label filter is still supported, but is marked for deprecation. This label filter is only relevant for filtering data in the views. In Browser Sessions, it will return pages that were accessed through a VPN where the gateway IP address is equal to the filter value. In Local Networks > Network Access, it will return probes to the VPN server where the gateway IP address of the VPN is equal to the filter value.
It will be fully removed from the product in a future release.
From te-browserbot version 1.146 and later, installation of an X11 server (via the te-xvfb package) is no longer mandatory. Existing Enterprise Agents will continue to have te-xvfb installed, unless users take action to remove the package. New Enterprise Agents will have the package installed by default, but this can be avoided using one of the following processes:
For Linux package installations: install_thousandeyes.sh now has a new command-line flag to skip te-xvfb package installation.
For Docker installations: Users may create new images based on the official ThousandEyes image that run
apt remove te-xvfb.For TEVA installations: Users may unlock their appliances and run
apt remove te-xvfb.
While it is now optional, users are still encouraged to keep the te-xvfb package installed. Some page load and transaction test configurations require starting Chromium without the --headless flag, and these situations will require te-xvfb.
Due to a change in service provider, customers with tests assigned to the IPv6 Cloud Agent in Dublin, Ireland will observe a corresponding change in path-visualization and source IP. The Cloud Agent ID used within the ThousandEyes API will remain unchanged. The new IPV6 IP is: 2001:4d40:4003::/48.
Endpoint Agent labels can now be updated via the API.
Users can now create Endpoint Agent scheduled tests via the API.
Previously, the Account group list API endpoint would only return the organizationName if the user was associated with multiple organizations. This has been changed, and the organizationName will now always be included.
The Import from JS File button in Transaction Test Settings has been replaced with a Create New dropdown menu. This dropdown retains the option to choose a local file to import, but also provides a selection of predefined template scripts. Clicking on an option will update the editor with the contents of the selected template script.
An issue was found where duplicate alerts were inadvertently being created, causing one of the alerts to fail to clear after resolution of the issue. This has been resolved.
An issue was found where updating proxy configuration would refresh disabled tasks, causing them to continue to run despite being disabled. This has been resolved. .
An issue was found where Cloud and Enterprise Agents reported no data on the Map view, even if data was being reported as expected. This has been resolved.
The digital certificates for app.thousandeyes.com and downloads.thousandeyes.com, which were previously issued by the DigiCert certificate authority, will be replaced with certificates from the QuoVadis certificate authority on October 13th, 2020. The replacement certificates will use certificate chains with larger key lengths (4096 bits) than the current certificate chain (2048 bits).
Customers who access these servers with clients (browsers, file transfer utilities, custom programs) that use older cryptographic libraries which cannot support 4096-bit key lengths should update their clients. Customers who use supported browsers or other current clients do not need to take any action.
Due to a change in service provider, customers with tests assigned to the Cloud Agent in Paris, France will observe a corresponding change in path-visualization and source IP.
We do not anticipate downtime or impact on test performance. The Cloud Agent ID used within the ThousandEyes API will remain unchanged.
The following Cloud Agent locations now have IPv6 support:
Paris, France
For a complete list of ThousandEyes Cloud Agent locations, see https://www.thousandeyes.com/product/cloud-agents.