Release Notes: March 2021
Last updated
Last updated
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 .
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.
, 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 .
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.
For example, before this change, the response JSON might read as follows:
After this change, the same JSON response will read as follows:
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.
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.
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.
