Changelog
You will not be able to add new Alert Grid widgets for dashboards after December 20, 2022. On January 20, 2023, the widget will be deprecated. The existing Alert Grid widgets will be removed from the platform and from the snapshots. ThousandEyes recommends you to replace these Alert Grid widgets with Alert List widgets if desired.
The custom webhooks now support Endpoint Browser Session alert types. You can now create custom webhooks and attach them to any Endpoint Browser Session alert rule.
- Browser Session tests from the Endpoint Agent has updated how Page Speed and Response times are calculated for pages where we get no response. Before, not fully accurate values were shown in the Page Speed and the wait time was shown as "Response Time". This was misleading because the browser never accessed to the page. These values have been updated to show a dash instead in those cases.
New Cloud Agents have been added to the following locations:
- Ashburn, VA, USA (Comcast) (IPv6)
- Ashburn, VA, USA (Verizon) (IPv6)
- Ashburn, VA, USA (AT&T) (IPv6)
- Chicago, IL, USA (CenturyLink) (IPv6)
- Chicago, IL, USA (Charter) (IPv6)
- Chicago, IL, USA (Verizon) (IPv6)
- Dallas, TX, USA (Comcast) (IPv6)
- New York, NY, USA (Comcast) (IPv6)
- San Jose, CA, USA (Charter) (IPv6)
- Endpoint Agent: An issue has been fixed in the Wireless tab of the Local Network tests in the Views section. When the user filters by Agents, the Endpoint Table is no longer incorrectly showing "No Data", and instead the results are now consistent with the BSSID Table.
- Endpoint Agent: The application of test configuration changes (e.g., changes of priority) in the Endpoint Agent has been improved and it will now take immediate action, or at last in the next check-in of the agent.
- Endpoint Agent: An issue that was showing an incorrect format for the retransmission rates in the Endpoint and BSSID tables of the Local Network tests has been resolved.
- Endpoint Agent: An issue has been fixed in the Automated Session Test (AST) widget of the Dashboard section. The filter by Target IP does now show the correct list of IPs available.
- Dashboard: Fixed an issue that was creating blank filters for some Dashboard widgets.
- Alerts: An issue that was preventing some customers in EU from assigning alert suppression windows to tests has been resolved.
- Account Management: An issue was allowing customers to create identical users in the same account. This has now been resolved, and an error is displayed, if an existing user gets created a second time.
- Revenue Platform: Fixed an issue in the usage consumption calculator that showed inaccurate unit consumption that did not match what customers saw when creating tests. This issue occurred specifically with agent-to-agent tests.
- Revenue Platform: An issue was causing a low response from the /v6/tests/#/test_update API. This has now been resolved and the previous response times have been restored.
- Browser Bot: Fixed issues related to the exclude domains feature on page load and transaction tests.
Additional advanced settings have been added for configuring page load and transaction tests:
- Exclude Domains and Object URLs: Users can now block requests to specific domains and object URLs. This excludes objects that are not important to the performance of your web page, or ensure third party tracking software is unaffected by your browser synthetic tests.
- Disable Screenshots: Users can now disable screenshots in a test.
- Set Browser Language: You can now set the browser language for your page load and transaction tests to verify the various language versions of your website or application.
- Set Page Loading Strategy: Some transaction tests have high timeouts because they need to wait for large assets to load in the browser before the next synthetic action can take place. Users can now adjust the page loading strategy so that synthetic actions are not delayed by non-critical assets. This lowers both the total necessary timeout length needed, and the variability in transaction time metrics.
- Emulate Microphone and Camera Input: This feature allows you to emulate a camera and microphone for web applications that require camera/microphone input.
- Allow Geolocation From Agent Vantage Point: This feature provides the geolocation of your agent for applications that require geolocation input.
In preparation for providing support for using IPv6 for agent communication between Enterprise Agents and the ThousandEyes Cloud, we will be adding IPv6 addresses as new AAAA records to our existing public production endpoints.
For the ThousandEyes package repositories, IPv6 will be used on platforms that preference IPv6 if you have a dual-stack configuration. For customers with proxies configured, your proxy configuration will determine whether agent traffic is sent via IPv4 or IPv6. All other agent communications are controlled by a flag in the Enterprise Agent configuration and should not be disrupted.
This change will occur on November 16th, 2022. The new IPv6 addresses can be found in our Firewall Configuration for Enterprise Agents and Static IP Addresses for ThousandEyes Repositories documentation.
ASN information is often very useful while troubleshooting a network issue. Having to look for the specific IP range related to a particular ISP always slows down all the network-related tasks. In order to make all these processes simpler, we have introduced support for ASN information in various parts of the Endpoint Agent:
- You can now filter agents by their ASN in the Agent Settings table. This way, you can identify the agents that are connecting from a specific ASN (ISP).
- Similar filtering has been added to agent labels. You can now associate a label with an ASN by searching for the AS by name or number.
- You can now filter test views by agent ASN, which lets you easily identify the test data that is specifically related to the agents associated with the ISP affected by the outage.
- Two new grouping options have been added to the Path Visualization tab. You can now group by both agent ASN and interface ASN, and identify whether an issue is related to a specific AS, as well as the affected agents.
ThousandEyes now supports configuring multiple interfaces on Cisco Catalyst devices, allowing a single Cisco Enterprise Agent to access multiple virtual networks, instead of deploying separate agents for each virtual network. This will benefit the SD-WAN users who want to measure performance across each WAN circuit.
For more information on multi-interface support, see Multi-Interface Support for Cisco Catalyst 9000 Switches.
ThousandEyes has updated its content subscription categories for product documentation. All existing subscriptions will be transferred to the new categories, and no action is required from customers.
The new categories are:
- New ThousandEyes Documentation
- Release Notes
- Privacy and Security
New Cloud Agents have been added to the following locations:
- Ahmedabad, India (Vodafone Idea)
- Ahmedabad, India (Vodafone Idea) (IPv6)
- Ashburn, VA (Cox) (IPv6)
- Ashburn, VA (CenturyLink) (IPv6)
- Chicago, IL (Cox) (IPv6)
- Los Angeles, CA (Cox) (IPv6)
- Paris, France (Orange)
- Paris, France (Orange) (IPv6)
- Seattle, WA (CenturyLink) (IPv6)
- An issue that caused certain hover panels in Internet Insights to display beyond the edge of the screen has been resolved.
- Cloud and Enterprise Agents: Fixed an issue where agent proxy information was displayed incorrectly in Views when a proxy is not used.
- Cloud and Enterprise Agents: Fixed an issue in the API that prevented the contentRegex property from being reset to empty in an HTTP server test.
- Dashboard: Fixed an issue where the Color Grid widget was using the wrong scale colors for Endpoint Agent automated session tests.
- Enterprise Agents: An issue that prevented custom appliances from detecting network interfaces in NUC11 physical appliances has been resolved.
- Revenue Platform: Fixed an issue in the usage consumption calculator that showed inaccurate unit consumption that did not match what users saw when creating tests. This issue occurred specifically with agent-to-agent tests.
- Fixed an issue where alerts were triggered incorrectly during an active alert suppression window.
- An issue has been resolved that impacted the reliability of NAT traversal while executing agent-to-agent tests against Webex Cloud Agents.
Automated session test data can now be used to generate dashboards. In particular, you can now use the data from both Network (Jitter, Loss, Latency, TCP Connection Count, VPN Loss, VPN Latency) and System (CPU and Memory Load) metrics together with the standard measures (Mean, Median, Average, Maximum, Minimum, nth Percentile, and Standard Deviation).
AST data is only available in the Grouped Bar, Table, Multimetric table, Number, Color Grid, Line, and Box and Whiskers widgets.
Endpoint Agent Views, the screen that shows all the results related to Endpoint Agent tests, has been improved in order to make troubleshooting tasks easier:
- The type of connection (Ethernet/Wireless), SSID and channel information has been added to the table of the Network tabs for scheduled and automated session tests. This way, you can easily correlate issues related to the quality of the wireless connection.
- We have added a new filter option on the Views page that allows users to define a filter for different network metrics (i.e., jitter, latency, packet loss, VPN latency, and VPN packet loss) to, for example, identify all the agents with latency over a threshold. This aims to make the identification of agents affected by a specific metric easier.
-
Two new buttons have been added to the Network > Table tab to help you in your troubleshooting workflow. Previously, the Network > Table tab helped you to identify the set of agents that were affected by a specific issue, but you could not easily select and filter them to focus on the data related to the affected agents. Now, with the addition of these two buttons, you can easily select agents and automatically create a filter for the whole view or specifically for the pathview.
- A new grouping option has been added to the Table tab for automated session tests. Unlike other types of tests, a single automated session test might target many different destinations (IP addresses) within the same test (Webex). To make the identification of the specific destinations affected by an incident easier, we now provide the ability to group tests by agent and also by agent and IP addresses.
You can now create, edit, and manage dashboards via a labeling system. You can create custom labels and assign them to specific dashboards, either via the dashboard selector or via the Dashboard Details page for a specific dashboard. You can then filter based on the created labels when using the dashboard selector for easy access to you favorite dashboards.
- We have slightly changed the behavior of our custom webhook testing functionality. Previously, the Test Status of an integration would not change from Success to Untested if a user made a change to an existing webhook that had successfully been tested. Now, if a user makes a change to the custom webhook form, except for changing the name of the webhook, the status will be changed to Untested until a user again successfully tests the integration.
New Cloud Agents have been added to the following locations:
- Chennai, India (Bharti Airtel)
- Chennai, India (Bharti Airtel) (IPv6)
- Kazan, Russia
- Kazan, Russia (IPv6)
- Los Angeles, CA, USA (CenturyLink) (IPv6)
- Los Angeles, CA, USA (Charter) (IPv6)
- New Delhi, India (Bharti Airtel)
- New Delhi, India (Bharti Airtel) (IPv6)
- San Jose, CA, USA (CenturyLink) (IPv6)
- San Jose, CA, USA (Cox) (IPv6)
- Sendai, Japan (IPv6)
- St. John's, Canada
- St. John's, Canada (IPv6)
- An issue, where the user API was sometimes incorrectly throwing a 4xx response when attempting to add a new user to an organization, has been resolved. This occurred when a user already existed in a different organization and was being added to a new organization. The user was still correctly being added, but our API was sending an incorrect response.
Reports and dashboards have now been merged into a single function. Reports has been removed from our lefthand navigation and all functionality has been consolidated into our Dashboards page. To find your previous reports, you can filter in the dashboard selector on Migrated Reports.
The Endpoint Agent View dashboard has been enhanced in order to make troubleshooting easier. These updates include:
- Improvements have been made to the search function for agents. In addition to agent name, you can now search by username, hostname, and IP addresses (both public and private).
- The tooltip for wireless information within the Network Access row will now show all the information related to the wireless information (i.e., SSID, Channel, Phy Mode) to make it easier to correlate data when troubleshooting issues related to it.
We have improved how our v6 and v7 dashboard APIs work as it relates to the time range specified in the API request. If the user provides a time range (from and to) in their API request to get widget data, the API will now return data for that time range. If the user does not provide a time range in the API request, the request will use the dashboard's defaultTimespan if globalOverride is set to true. If globalOverride is set to false, then the API will return data for the individual widget time settings set by the user or the default time range (1 day) if no value is set for the individual widget. The user can change defaultTimespan and globalOverride values using the UI or the dashboardupdate endpoint of the v7 API.
Our custom webhooks now support Endpoint Scheduled Test alert types. You can now create custom webhooks and attach them to any Endpoint Scheduled Test alert rule. We have also improved the Alert Rules page under Alerts. As we continue to scale out the types of alert rules supported, we have added a specific alert type group selector when assigning alert rules for an integration.
New Cloud Agents have been added to the following locations:
- Ahmedabad, India (Bharti Airtel)
- Ahmedabad, India (Bharti Airtel) (IPv6)
- Chicago, IL, USA (IPv6)
- Dubai, UAE (AWS me-central-1)
- Jakarta, Indonesia (IPv6)
- Kazan, Russia
- kazan, Russia (IPv6)
- Lagos, Nigeria (IPv6)
- New Delhi, India (Vodafone Idea)
- New Delhi, India (Vodafone Idea) (IPv6)
- St. John's, Canada
- St. John's, Canada (IPv6)
- Yogyakarta, Indonesia
- Yogyakarta, Indonesia (IPv6)
- Device Discovery now correctly shows an error message when a newly discovered device is a duplicate of a monitored device.
- An issue that caused the browser back button to not work as expected on the Internet Insights Overview page has been resolved.
- An alert rules issue for Devices, that prevented the interface selection dropdown from correctly appearing in account groups with large numbers of monitored interfaces, has been resolved.
- An issue that was temporarily preventing our EU region customers from accessing the "Integrations" page in product has been resolved.
In Cloud & Enterprise Agents > Test Settings > Advanced Settings, the Verify SSL certificate field now applies to both the HTTP view and the page load or transaction view in page load and transaction tests.
Previously, the Verify SSL certificate setting for these test types did not apply for the entire test, but held for the HTTP server view only. As a workaround, customers had to configure the agent-level settings.
As part of this change, starting December 6, 2022, we will begin deprecating the agent-level option at Cloud & Enterprise Agents > Enterprise Agents > Agent Settings > agent-name > Verify SSL certificates for browser tests.
In cases where the test-level option is de-selected but the agent-level option is not de-selected, the ThousandEyes platform will continue to apply the agent-level setting until December 6, 2022.
After that date, all web-layer tests will follow the configuration you have set in Test Settings. The agent-level setting will be removed.
Most browser-based tests will not require changes. But if your page load and transaction tests have SSL verification disabled, review your configuration and use the test-level setting going forward.
New Cloud Agents have been added to the following locations:
- Anchorage, AK, USA
- Cleveland, OH, USA
- Cleveland, OH, USA (IPv6)
- Cleveland, OH, USA (Charter)
- Cleveland, OH, USA (Charter) (IPv6)
- Surabaya, Indonesia
- Surabaya, Indonesia (IPv6)
In addition, we've added AWS Cloud Agents in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- Boston, MA, USA (AWS Local Zone) (AWS us-east-1-bos-1)
- Chicago, IL, USA (AWS Local Zone) (AWS us-east-1-chi-1)
- Dallas, TX, USA (AWS Local Zone) (AWS us-east-1-dfw-1)
- Denver, CO, USA (AWS Local Zone) (AWS us-west-2-den-1)
- Houston, TX, USA (AWS Local Zone) (AWS us-east-1-iah-1)
- Kansas City, MO, USA (AWS Local Zone) (AWS us-east-1-mci-1)
- Las Vegas, NV, USA (AWS Local Zone) (AWS us-west-2-las-1)
- Los Angeles, CA, USA (AWS Local Zone) (AWS us-west-2-lax-1)
- Miami, FL, USA (AWS Local Zone) (AWS us-east-1-mia-1)
- Minneapolis, MN, USA (AWS Local Zone) (AWS us-east-1-msp-1)
- New York, NY, USA (AWS Local Zone) (AWS us-east-1-nyc-1)
- Philadelphia, PA, USA (AWS Local Zone) (AWS us-east-1-phl-1)
- Phoenix, AZ, USA (AWS Local Zone) (AWS us-west-2-pdx-1)
- An issue was fixed in the Update Tests API that prevented updating the port in Agent to Server tests if the server wasn't also specified.
- An issue was resolved that was preventing some dashboards from automatically updating every two minutes.
Customers can now generate snapshots for multi-service views they have configured. For more information on multi-service views, see Multi-Service Views.
The Recorder IDE and all Cloud and Enterprise Agents with auto-updates have been upgraded to use Chromium 97 with BrowserBot (v2.6.0+) and Recorder IDE v1.4.0.
Between Chromium v80 (BrowserBot v2.5.9 and prior) and Chromium v97, notable differences include:
- Recorder IDE stability on macOS devices.
- After an iframe is destroyed, Selenium WebDriver will no longer switch to the default content automatically.
- HTML elements with an area of zero are no longer clickable.
- shadowRoot no longer returns a WebElement.
- ChromeDriver does not wait for the HTML document to be loaded completely.
The upgrade to the NPCAP library on the Endpoint Agent client for Windows will now be done on September 28, 2022, and not on September 17, 2022, as communicated previously.
The ThousandEyes Support chat has been replaced by the new chatbot service, TEACH (ThousandEyes Assistant, Concierge, & Helper). For more information about TEACH, see Live Chat.
New Cloud Agents have been added to the following locations:
- Bangalore, India (Bharti Airtel)
- Bangalore, India (Bharti Airtel) (IPv6)
- Bangalore, India (Vodafone Idea)
- Bangalore, India (Vodafone Idea) (IPv6)
- Chennai, India (Vodafone Idea)
- Chennai, India (Vodafone Idea) (IPv6)
- Mumbai, India (Bharti Airtel)
- Mumbai, India (Bharti Airtel) (IPV6)
- Northampton, England (IPv6)
- An issue that caused edited dashboards to not save correctly after a refresh has been resolved.
- An issue that prevented refresh tokens from being generated for oAuth client credential authentication in custom webhooks has been fixed.
- An issue has been resolved where the filter options were not populating correctly on our live status widgets for dashboards.
- An issue that was causing reports in Japanese that were downloaded in PDF to be formatted incorrectly has been resolved.
- An issue was found where several group by options for our Endpoint Agent report and dashboard widgets were not available. This has now been corrected. The list of missing group bys were as follows:
- Gateway
- SSID
- BSSID
- VPN Vendor
- VPN Gateway
- Proxy Address
- DNS Server
- Session Errors
- IP Address
- An issue that was incorrectly triggering dynamic baseline alerts that had multiple dynamic alert conditions attached to it, whether in the same rule or in multiple different rules, has been resolved.
- An issue was identified where timestamps for individual schedule HTTP server tests in the Endpoint Agent were not taking into account the user's timezone. This has been resolved, and you will now see the correct timestamps associated to each test taking into account the specific timezone.
We are happy to announce general availability of our new custom webhooks feature! You can find custom webhooks under the Alerts > Integrations menu. With custom webhooks, you can
- Ingest our alert webhook into any third-party system that supports incoming webhooks, including Cisco Webex, Microsoft Teams, and Splunk.
- Define the structure of the webhook payload to your liking, including fully customizable headers, URL query parameters, and JSON payload.
- Add static key : value pairs or dynamic variables based on your needs to any portion of the webhook payload.
This feature is currently available only for our Cloud and Enterprise Agent alerts and only supported via the ThousandEyes UI. API and additional alert type support will come in the near future. You can read more about this feature in our documentation.
BrowserBot v2.6.0+ provides an upgrade to the Chrome browser used in the BrowserBot agent to run page load and transaction tests.
With the conclusion of the BrowserBot Early Track Program, all BrowserBot agents are being upgraded to v2.6+ with Chromium v97, quickly followed by an upgrade to the Recorder IDE. This change will improve IDE stability for macOS devices, and will enable additional features for browser tests from Chrome.
We've identified 3 edge cases where the scripting syntax has changed between Chromium v80 (prior to BrowserBot v2.6.0) and Chromium v97 (BrowserBot v2.6.0 and after):
- After an iframe is destroyed, Selenium WebDriver will no longer switch to the default content automatically.
- HTML elements with an area of zero are no longer clickable.
- shadowRoot no longer returns a WebElement.
We have reached out to all identified customers affected by these script changes. Contact ThousandEyes Support if you need additional assistance.
Over the next few months, we will be removing access to public snapshots that were made available via link sharing and that have not been accessed in over 365 days. This is part of our broader strategy to ensure a strong security posture for our customers. You will still be able to access these snapshots in the ThousandEyes platform, just not via the publicly accessible URL. After this change, these snapshots will be accessible as private snapshots, under Sharing > Saved Events.
We also plan to eventually delete any public snapshots that have not been accessed in 365 days entirely from the platform. If you don't want public snapshots affected by this change to be auto-deleted, you should access them to reset the time count since last access.
Both of these changes will impact all test snapshots, Endpoint Agent snapshots, Internet Insights snapshots, device snapshots, and report snapshots that have link sharing enabled and are available via a public URL. There is no action required on your part. In the future, we will introduce the option for you to define, at the time of snapshot creation, how long you want the snapshot to be active.
The new auto-detect feature, currently in open Beta, now provides full support for all AST applications (i.e,. Webex, Zoom, and MS Teams).
Auto-detect is a new feature that allows you to automatically select the best configuration to monitor the selected application in ASTs, making the monitoring of applications with your Endpoint Agents much easier.
When configuring an automated session test within the Endpoint Agents > Tests Settings dashboard, you will now see an auto-detect option under Protocol, which will automatically select the most reachable protocol for the selected application.
In order for auto-detect configuration to work correctly, you must have the TCP driver installed.
We've made a change in how we rebalance tests in agent clusters when round-robin is enabled, to take into account test sub-intervals. This change improves the reliability of round-robin enabled tests and improves balancing of tests across agent clusters.
New Cloud Agents have been added to the following locations:
- Cordoba, Argentina (IPv6)
- Osaka, Japan (KDDI) (IPv4)
- Oskaka, Japan (KDDI) (IPv6)
- Seoul, South Korea (LG Telecom)
- Singapore (Singtel)
- Singapore (Singtel) (IPv6)
- An issue that affects agent-to-agent tests conducted from the ThousandEyes Virtual Appliance (TEVA) in environments where the originating agent has IPv6 disabled in the kernel has been resolved. This issue would have impacted any TEVAs deployed that had IPv6 disabled in the kernel at boot-time, but would not have impacted TEVAs that had no IPv6 interface available, where a fallback would have already occurred.
- We have added validation to both our classic and custom webhooks that prevents users from sending webhooks to private IP addresses.
All BrowserBot agents with auto-upgrade enabled have been upgraded to version 2.5.7+ to leverage the new BrowserBot containerized architecture that uses Podman. This improves security and sets the foundation for future browser test capabilities.
As mentioned in the November 2021 Release Notes, the keep browser cache between tests option has been deprecated, and these page load and transaction tests will reset the browser cache between all browser test rounds. This option is no longer available from the Agent Settings page, in BrowserBot starting from v2, and is no longer functional via the API.
Amazon Linux 2 will also no longer be supported by BrowserBot starting with v2 onwards.
We have added several new features to our dashboard page in order to ensure parity between our dashboard and reports objects, with the goal of de-commissioning our reports page entirely in 30 days. All of your existing reports will now be available in the dashboard page and we strongly encourage you to stop using reports and only use dashboards moving forward.
For parity's sake, with our dashboards, you can now:
- 1.Download your dashboard and widget data into a CSV or as a PDF.
- 2.Create or schedule a snapshot of your dashboards.
- 3.Save an individual widget as an image.
- 4.Add a detailed description to a dashboard in the administration page of the dashboard.
- 5.View and edit all of your existing reports in the dashboard page.
We have also added a few new features as we work towards merging the two objects:
- 1.We have updated our dashboard selector to now match the look and feel of our test selector. You can better filter based on sharing permissions and built-in dashboards.
- 2.You can now override the individual widget time selections and apply a consistent time selection to all widgets in a dashboard.
- 3.We have added a spinning timer to let you know when your data will be refreshed.
Note that the live action dashboard widgets (alert list, alert grid, test table, and agent status) cannot be viewed in a fixed timespan. Additionally, the test table widget will always only display data on a 12-hour running period, the alert grid widget will always only show data on a 24-hour running period, and the agent status widget will always show a live status of the agents displayed.
Previously, when you reinstalled an Endpoint Agent on a device, the agent was registered as an entirely new agent in ThousandEyes. As a result, apart from perhaps seeing agents with duplicate names, you also had their data disjointed between the new and the old agent, making it very difficult to correlate the historical data between them.
With the new reinstallation key included in the agent installation process, ThousandEyes will automatically check whether there is an existing agent with the same hostname, and consolidate their data into a single one. The detailed reinstallation procedure can be found here.
The Endpoint API now includes all the agent interfaces' information in the Endpoint Agent API endpoints. In particular, you can now obtain all the available information that ThousandEyes has about the agent interfaces (for example, interface name, IP address, gateway, link speed, BSSID, SSID, and PHY mode).
New Cloud Agents have been added to the following locations:
- Liege, Belgium (Proximus)
- Liege, Belgium (Proximus) (IPv6)
- Mumbai, India (Vodafone Idea)
- Mumbai, India (Vodafone Idea) (IPv6)
- An issue was found that was resetting the Assigned Agents (24h) field in the Test Settings page from the Endpoint dashboard when a scheduled test was saved. The issue has been resolved and the field now shows the correct value.
- An issue was found where changing between nodes that were labelled with IP Address and ASN would not immediately take effect in the path visualization of the Endpoint Views dashboard. This has been resolved.
- An issue was found where we were incorrectly showing a 24 hour timespan in our report download PDFs, even though the data represented was for a different timespan. This was a simple header mistake, as the data was showing correctly based on the desired configuration, and has been resolved.
- An error in our v6 reports API was sending an incorrect value for dataComponentID in our response. This lead to customers then requesting the incorrect dataComponentID and receiving a 404 response from our API. This issue has been resolved.
- An issue that was incorrectly showing the alert severity of some Endpoint alert rules as Info, even though they were assigned different severity values in their alert rule configuration, has been resolved.
ThousandEyes is pleased to announce the general availability of our EU region data centers. With this release, customers based in the EMEA region will have the option to onboard to our EU region, which will enhance the performance, scalability, and resilience of the ThousandEyes platform, and allow customers to address any regulatory concerns they have that require SaaS or Cloud services to be based in the EU.
If you would like to understand more about this announcement, see the Multi-Region Cloud Support documentation, or reach out to your account team's Customer Success Manager.
Enterprise Agents connecting to the EU Region's infrastructure will require new hosts to be whitelisted in the firewall. For more information, see Firewall Configuration for Enterprise Agents.
Automated Session Tests from Endpoint Agents can now be included in Endpoint Snapshots. Together with Scheduled Tests, Browser Sessions, and Local Network, you will be able to save a snapshot carrying the necessary information related to the specific set of tests that you have defined. In addition, you can still define the data range, the anonymization of the data that identifies users, and whether you want to generate the link to share it with third-parties.
The NPCAP library on the Endpoint Agent client for Windows will be upgraded to version 1.55 on September 17, 2022. This library is required by users to leverage TCP network tests. The manual upgrade for testing is available now. You can learn more about this upgrade and how to test it here.
New Cloud Agents have been added to the following locations:
- Antwerp, Belgium (Proximus) (IPv4)
- Antwerp, Belgium (Proximus) (IPv6)
- Bangkok, Thailand (Alibaba ap-southeast-7)
- Gävle, Sweden (Azure swedencentral)
- Hong Kong (HKT) (IPv4)
- Hong Kong (HKT) (IPv6)
- Jakarta, Indonesia (AWS ap-southeast-3)
- Jersey City, NJ, USA (IPv4)
- Jersey City, NJ, USA (IPv6)
- Madrid, Spain (GCP europe-southwest1)
- Midlothian, TX, USA (GCP us-south1)
- Milan, Italy (GCP europe-west8)
- New Albany, OH, USA (GCP us-east5)
- Paris, France (GCP europe-west9)
- Phoenix, AZ, USA (Azure westus3)
- Santiago de Chile, Chile (GCP southamerica-west1)
- Seoul, South Korea (Alibaba ap-northeast-2)
- Tokyo, Japan (NTT) (IPv4)
- Tokyo, Japan (NTT) (IPv6)
- An issue was identified when migrating Endpoint labels to the new system. A small subset of customers had an additional set of labels created incorrectly. These labels were removed and did not cause any service impact.
At 8:00 UTC time on July 11, 2022, certain Cloud Agents in China began experiencing high packet loss to both configured DNS resolvers. This is representative of conditions that occur in this geographic region. DNS resolution also affected the ability to submit Cloud Agent data to the ThousandEyes Platform.
Between July 13, 2022 at 00:40 UTC and July 13, 2022 at 05:40 UTC, the Cloud Agent operations team took action to enable data submission by updating the DNS resolver for affected locations to 114.114.114.114, which is a DNS resolver in China Unicom's ASN. This change enabled data collected to be successfully submitted to the ThousandEyes platform.
An expected side-effect of this change is that certain tests' DNS resolution behavior may have changed due to using different resolvers. Our product and engineering teams continually assess DNS performance in China and from their tests, they found the most reliable DNS open resolver is aliDNS (223.6.6.6). This is an anycast solution, so we expect good reliability from it moving forward, using 223.6.6.6 as a primary and 114.114.114.114 as a secondary DNS resolver for the following Cloud Agents in China:
- Beijing, China (China Mobile)
- Beijing, China (China Telecom)
- Beijing, China (China Unicom)
- Changsha, China (China Mobile)
- Chengdu, China
- Chengdu, China (China Mobile)
- Chongqing, China (China Mobile)
- Dalian, China (China Unicom)
- Foshan, China
- Guangzhou, China
- Guangzhou, China (China Mobile)
- Guangzhou, China (China Unicom)
- Jinan, China (China Unicom)
- Nanjing, China
- Ningbo, China (China Mobile)
- Shanghai, China (China Mobile)
- Shanghai, China (China Telecom)
- Shanghai, China (China Unicom)
- Shenyang, China (China Unicom)
- Shenzhen, China (China Mobile)
- Shenzhen, China (China Unicom)
- Shijiazhuang, China (China Unicom)
- Tianjin, China (China Mobile)
- Wenzhou, China (China Telecom)
- Wuhan, China (China Telecom)
- Wuxi, China
- Xi'an, China (China Telecom)
- Zhengzhou, China (China Mobile)
This change took place on the 25th of July, 2022 at 16:00 UTC.
Last modified 2d ago