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.
Proxy Metrics Added to Dashboards, Reports, and HTTP Server View
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.
TEPi 8GB Support
The ThousandEyes Raspberry Pi installation image has been updated to support the 8GB version of the device.
Updated Virtual Appliance Image
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.
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.
2020-11-12 Bug Fixes
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.