Release Notes: November 2023
Last updated
Last updated
We're providing an option to run page load and transaction test with Chromium 118 (in addition to the current Chromium 97) used in the Recorder IDE and on ThousandEyes Cloud and Enterprise Agents. This allows customer to try out newer versions of Chromium before we roll out to all agents to ensure continuity of their tests page load and transaction tests across versions.
The customer-facing action items are as follows:
Agent auto-updates: We are strongly encouraging all customers to allow agent auto-updates. If you choose not to enable automatic updates to your enterprise agents, you might see an increase in test failures as a result.
New test settings and agent settings: To try designated priority tests in the new version of Chromium, create a disabled duplicate version of your test, select your dual Chromium agents from the agent list, and run an instant test to see the results. If you want to test the newer version of Chromium on Enterprise Agents, you must also set the Browserbot Package Type to "Dual Chromium Version" in Agent Settings, so that the agent is capable of using the newer version of Chromium.
See docs pages for more information.
The changes are visible on the following ThousandEyes screens:
Cloud & Enterprise Agents > Test Settings for page load and transaction tests
A new Chromium option under Browser Options in Advanced tab has options for Default and Use newer when available.
Cloud Agent selection in test settings indicates which Cloud Agents have the Dual Chromium option enabled.
Enterprise Agent Settings: A new BrowserBot Package Type setting has options for Default and Dual Chromium Version.
Recorder IDE will have options for Default and Newer.
Templates with transaction tests now support the "web-transactions" test type.
Long test names are now fully visible in template side panel. This fixes an issue where the name on the side panel was truncated so that users could not easily determine which test to disable.
WAN Insights now supports closed-loop automation for recommendations, with click-through navigation to vAnalytics and vManage, where the recommended path changes can be applied within a structured workflow. Note that vManage 20.12 or higher is required.
WAN Insights users who have upgraded to vManage 20.12 or higher can take swifter action on WAN Insights path recommendations. Click Request to Apply in WAN Insights to highlight the recommendation you want to apply in vAnalytics. Then, the vAnalytics click-through workflow directs users to vManage, allowing them to review and apply the recommended AAR policy changes to their network.
Before deployment, users can inspect and compare suggested network policy changes with the current configuration, to ensure that the recommended path changes meet network performance requirements.
If a rollback is required, you can revert back to the original policy settings by locating the recommendation in WAN Insights and clicking Request to Revert.
Meraki customers with an Advanced Security or SDWAN+ license now have access to deploy ThousandEyes Enterprise Agents to their supported Meraki MX networks through the Meraki dashboard. Meraki users can now benefit from enhanced visibility at scale and alerting capabilities by creating customized network and application testing for critical applications using the ThousandEyes platform. To deploy an Enterprise Agent to a Meraki MX network, that network must meet certain minimum criteria such as the firmware version of the device and the model of the device associated with the network.
Customers using custom webhooks will need to update their ID fields to accept string values. Modify your systems to interpret IDs as strings, enclosed in quotation marks; for example, from "id": {{id}} to "id": "{{id}}". For those who deserialize any ID fields as numeric, or if your webhook receiver cannot otherwise handle a 128-bit string value, we strongly advise verifying your system's compatibility with this new format. If your current tool for accepting webhooks from ThousandEyes does not support the new UUID format, make the necessary adjustments or take appropriate actions as soon as possible.
The existing process that logs the connect/disconnect events for the Global Protect VPN product is updated to support upcoming features.
When running an in-session path trace, the probe did not always stop after receiving an RST response. The RST response is now fully handled.
The X-ThousandEyes-Agent header is now set to Yes by default to address the user feedback regarding HTTP tests.
During certain Webex AST data rounds, erroneous multiple active media nodes were identified, causing integration issues between Control Hub and ThousandEyes. This has now been resolved.
An issue resulting from a recent update to F5's VPN client, causing failure to identify a device connected to F5 VPN, has been resolved.
Version 1.175.0 brought an enhancement to probe only those VPN servers that are presently active and used by the host machine. However, it resulted in a problem in the VPN probe collection, where the path visualization did not display the VPN icon in some conditions. This release fixes the issue and restores the correct display of the VPN icon.
To enhance the availability and resilience of our global platform, we are introducing the US2 region (Columbus, Ohio, USA). Onboarding of new customers to the US2 region will commence in the near future. Customers interested in migrating to the US2 region should contact their account team. No action is required for customers in our existing US1 (formerly US) and EU1 (formerly EU) regions.
With the addition of the US2 region, we have renamed the existing US and EU regions to US1 and EU1 respectively, to improve clarity.
For customers who manage organizations across multiple regions, you will notice this adjustment in the Current Region field, located in the Account drop down at the top of your screen.
Customers using the Force SYN probe option in scheduled tests can now select the Path trace in session option. While the "auto" option remains suitable for most customers, the path trace in session option enables customers to troubleshoot specific scenarios under specific network conditions.
You can now exclude subdomains from the monitoring domains, which gives you more control over your monitoring experience with Endpoint Agent browser sessions.
Previously, you could only specify which domains you wanted to monitor when the end-user accesses them, but not exclude specific subdomains from being monitored. With this new capability, you can now exclude unwanted subdomains from the monitoring domain.
This new capability provides greater flexibility and efficiency in managing your monitoring preferences. Whether you have subdomains that are not relevant to your monitoring objectives or you want to focus on specific aspects of your website, this feature enables you to refine your monitoring strategy according to your unique needs.
Brasilia, Brazil (Claro)
Brasilia, Brazil - IPv6 (Claro)
Brasilia, Brazil
Brasilia, Brazil - IPv6
Manila, Philippines - IPv6 (PLDT/Smart)
Resolved an issue where an agent was added to the global alert when it violated the metric condition in the final round, regardless of whether it met the overall round condition.
To improve load times, clicking on Data suppressed tooltips now redirects to the Alert Suppression page.
See for details.
For more information, see .
As , we have transitioned all notification IDs associated with webhook integrations from a numeric value to a string-based UUID format. This change was completed on November 18th, 2023, at 10:42 PM UTC.
We've included US2 region IP addresses in our firewall exception lists for and .
For more information about the US2 region, see the .
For more information, see .
Instead of changing filter values on each widget of a dashboard, users can leverage dashboard filters to change the values of multiple widgets that are connected to the Cloud and Enterprise Agent data source. This feature is in Limited Preview, you can learn more about it . Contact your account team to get access to dashboard filters.
The ThousandEyes v7 API is entering Limited Preview. Our v7 API brings new capabilities for developer- and DevOps-focused customers from standardization to performance and improved documentation, to deliver a single cohesive API surface for all ThousandEyes product areas. To get started, visit our .
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see .