Comment on page
Changelog
You can now deploy a template containing a SIP server test via the API. Overriding SIP server test settings when deploying via API is also supported.
- Fixed an issue where tooltips were showing when their corresponding elements were not hovered.
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.
- We've included US2 region IP addresses in our firewall exception lists for Custom Webhooks and Enterprise Agents.
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.
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 here. 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 v7 API docs.
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- 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.
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.
As previously announced, 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.
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.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.
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.
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.
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.
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.
We have released a new Cloud and Enterprise Agent test template for deploying a suite of ThousandEyes tests to monitor Microsoft Teams. See the Monitoring Microsoft Teams guide for more information.
ThousandEyes now supports installing Enterprise Agents on Intel NUC 12 and NUC 13 devices. For more information on installation processes and hardware requirements, see Installing a Physical Appliance.
We have introduced a limitation on the number of groups that can be plotted in widgets. For variables with high cardinality (more than 50 unique groups), use widget filters to narrow down the groups.
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- Auckland, New Zealand (AWS Local Zone)
- Auckland, New Zealand (Spark NZ)
- Berlin, Germany (GCP europe-west10)
- Fuzhou, China (Alibaba cn-nanjing)
- Manila, Philippines (AWS Local Zone)
- Manila, Philippines (Globe-Innove)
- Nanjing, China (Alibaba cn-nanjing)
- Riyadh, Saudi Arabia (Alibaba me-central-1)
- Tel Aviv, Israel (AWS il-central-1)
- Warsaw, Poland (Azure polandcentral)
This is a final reminder. As previously announced, on October 31, 2023 - today, ThousandEyes will discontinue support for the following IP addresses:
- 52.52.142.26
- 52.52.36.83
If you are currently allowlisting these IP addresses to receive alert notifications, you should continue to do so until October 31, 2023. However, to avoid a hard stop on your incoming ThousandEyes webhooks, we urge you to update your systems to also allow any or all of the following addresses based on your region:
US1 Region
- 13.56.245.241
- 52.9.183.148
- 18.232.232.61
- 35.168.54.3
- 107.22.84.44
- 3.220.243.232
- 3.218.27.195
- 3.221.227.188
EU1 Region
- 18.157.124.37
- 3.70.3.30
- 18.156.17.238
- 18.158.163.183
- 35.158.19.241
- 3.127.8.252
- 46.51.169.205
- 54.75.173.76
- 54.217.22.60
- 34.243.129.225
- 54.216.15.243
- 108.128.60.238
After October 31, we strongly advise you to remove 52.52.142.26 and 52.52.36.83 from your allowlist, as we will no longer support them.
- Removed the "Look Up Servers" form inputs for DNS trace tests, which were causing an erroneous validation error when left blank. DNS trace tests do not have a list of target servers to test, so this field is not necessary.
Cisco has publicly released a security advisory related to the HTTP Server component in IOS-XE: Cisco Security Advisories.
Until this vulnerability is resolved, the impact to ThousandEyes Enterprise Agents is covered below:
While disabling this component does have an impact on the ability to manage the Cisco Application Hosting Framework (also referred to as CAF, IOX, or App Hosting) from the DNA Center (DNAC) environment, it does not directly impact the ability to run a ThousandEyes Enterprise Agent on the Cisco device.
We have done several tests to verify that both existing and new installs of the ThousandEyes Enterprise Agent conducted using the command line interface (CLI) for CAF will not be negatively impacted by disabling the HTTP server component within IOS-XE as specified in the security advisory. That said, our current recommendation is that customers who intend to use DNAC or other external tooling to manage their Cisco network devices follow the instructions within the security advisory to utilize an ACL to only allow trusted devices to access the HTTP server component.
If you have any questions or concerns, please contact ThousandEyes Support.
- Fixed an issue where the Review button was enabled even though the user needed to take action to fix an error.
Support has been added for the following test metrics:
Endpoint Agent HTTP tests:
- Availability
- Response Time
- Throughput
Endpoint Agent network tests:
- Loss
- Latency
- Jitter
Users can now enable in-session mode for agent-to-server test types (HTTP server, FTP server, page load, transaction, DNS server, and network) to get an accurate path trace when Force TCP SYN mode is selected for end-to-end network probes. This corrects behavior where phantom packet loss could be encountered with some firewall vendors in their default configuration.
To enable this option on an agent-to-server test, select Force SYN as the probing mode, and check the In Session box under Path Trace Mode.
For other test types, the same option is available under the Network section of the Advanced Settings tab.
We have added support for IP address enrichment for cloud-based targets, in collaboration with Amazon Web Services (AWS). IP addresses can now be more accurately identified across the global AWS edge network. Additionally, AWS end services will be enriched for better identification like AWS S3, EC2, CloudFront, Route 53, and Global Accelerators. For more information, see Path Visualization for Cloud Networks.
As previously announced, on October 31, 2023, ThousandEyes will discontinue support for the following IP addresses:
- 52.52.142.26
- 52.52.36.83
If you are currently allowlisting these IP addresses to receive alert notifications, you should continue to do so until October 31, 2023. However, to avoid a hard stop on your incoming ThousandEyes webhooks, we urge you to update your systems to also allow any or all of the following addresses based on your region:
US1 Region
- 13.56.245.241
- 52.9.183.148
- 18.232.232.61
- 35.168.54.3
- 107.22.84.44
- 3.220.243.232
- 3.218.27.195
- 3.221.227.188
EU1 Region
- 18.157.124.37
- 3.70.3.30
- 18.156.17.238
- 18.158.163.183
- 35.158.19.241
- 3.127.8.252
- 46.51.169.205
- 54.75.173.76
- 54.217.22.60
- 34.243.129.225
- 54.216.15.243
- 108.128.60.238
After October 31, we strongly advise you to remove 52.52.142.26 and 52.52.36.83 from your allowlist, as we will no longer support them.
We have released a new Cloud and Enterprise Agent test template for deploying a suite of ThousandEyes tests to monitor Microsoft 365. See the Monitoring Microsoft 365 guide for more information.
We have made an update to the existing notification regarding snapshot expiration. The update includes the addition of "Dashboard" as a prefix to the notification. This change helps to reduce any confusion that might arise from other snapshot expiration notifications, such as those for the Endpoint Agent. With the new update, the notification will be more specific and will read as follows: 6 Dashboard Snapshots Expiring within 30 days.
ServiceNow, PagerDuty, and Slack integrations are now exclusively managed on the Integrations page. Users can no longer create or manage these integrations from the alert rule Notifications tab. However, the option to assign integrations to alert rules is still available on the alert rule Notifications tab.
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- New Orleans, LA, USA (IPv4)
- New Orleans, LA, USA (IPv6)
- Winnipeg, Canada (Telus)
- Winnipeg, Canada, (Telus) (IPv6)
- Resolved an issue that was showing erroneous HTML tags in the popup message for certificate errors detected by the Endpoint Agent browser session tests.
- Fixed an issue that was incorrectly adding the "Copy" suffix to Endpoint Agent labels while generating dashboards using this data.
- Fixed an issue in the time series widget of the dashboards where the drill-down URL was missing the
agentId, resulting in redirecting to the incorrect view.
Error and warning messages for resolving duplicate test names are now clearer.
The Cisco Secure Client ThousandEyes Endpoint Agent module for macOS is available from September 11, 2023. For instructions on accessing and installing the module, see Secure Client Integration.
As previously announced, on October 31, 2023, ThousandEyes will discontinue support for the following IP addresses:
- 52.52.142.26
- 52.52.36.83
If you are currently allowlisting these IP addresses to receive alert notifications, you should continue to do so until October 31, 2023. However, to avoid a hard stop on your incoming ThousandEyes webhooks, we urge you to update your systems to also allow any or all of the following addresses based on your region:
US1 Region
- 13.56.245.241
- 52.9.183.148
- 18.232.232.61
- 35.168.54.3
- 107.22.84.44
- 3.220.243.232
- 3.218.27.195
- 3.221.227.188
EU1 Region
- 18.157.124.37
- 3.70.3.30
- 18.156.17.238
- 18.158.163.183
- 35.158.19.241
- 3.127.8.252
- 46.51.169.205
- 54.75.173.76
- 54.217.22.60
- 34.243.129.225
- 54.216.15.243
- 108.128.60.238
After October 31, we strongly advise you to remove 52.52.142.26 and 52.52.36.83 from your allowlist, as we will no longer support them.
WAN Insights now offers extended support for vManage Cloud OnRamp (CoR) applications. For all WAN Insights users who are using vManage's CoR feature to route traffic to SaaS applications in the cloud via Direct Internet Access (DIA), this enhancement adds a seamless way to onboard CoR applications into WAN Insights using WAN Insights' existing workflow for adding new applications.
To onboard CoR applications into WAN Insights, first onboard your CoR applications in vManage. Within 24 hours, your application will show up in WAN Insights, ready for onboarding using the Add new application workflow as described in Adding Business-Critical Applications to WAN Insights.
With the addition of CoR applications, you can now monitor the health and performance of your DIA paths using WAN Insights' comprehensive quality score, troubleshoot reported issues more quickly, and review path recommendations to improve path quality and user experience.
The integrations with PagerDuty and Slack for alert notifications are now available on the Integrations page. Users can still create, edit, and assign these integrations to alert rules from the alert rule's Notifications tab. In the future, these integrations will be created and managed exclusively via the Integrations page. However, the ability to assign integrations to alert rules will still be accessible from the alert rule's Notifications tab.
Support has been added for the following test metrics:
RTP stream tests:
- MOSS
- Loss
- Discards
- Latency
SIP server tests:
- Availability
- Response Time
- Total Time
As previously announced, new default alert rules will roll out to all customers within the next 5 days. These alert rules will be displayed with a suffix "2.0" in the alert rule name. Any new tests that users create will automatically be associated with the new set of default alerts. Existing tests will continue to use the old set of default alert rules and will remain unaffected. This change will show up in the activity logs as updated by "ThousandEyes Support."
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- Amsterdam, Netherlands (Lumen)
- Amsterdam, Netherlands (Lumen) (IPv6)
- Manila, Philippines (PLDT/Smart)
- London, England (Lumen)
- London, England (Lumen) (IPv6)
- Resolved an issue that prevented some users from being added to an account group. This issue affected users whose email was first added to the external mailing list for alert notification purposes and was then added to a new or existing user.
- Fixed an issue in the Time Series Stacked Bar Chart dashboard widget where the Page Load metric was not showing as a selectable option.
- In a recent update to the Webex client, the location of the identifier used when integrating Control Hub with ThousandEyes for Webex meeting data was changed. As a result, some users could see the automated session test data for Webex meetings in the ThousandEyes UI, but could not see the corresponding network path data in Control Hub. The issue is resolved in Endpoint Agent client version 1.68.2.
ThousandEyes can now display user-defined templates in the Test Templates UI. Creation of user-defined templates is supported through the API. When a user creates a test template, all users within the same account group will have the option to select it when deploying a new test template. For more information about user-defined test templates, see User-Defined Test Templates.
When you deploy a test template using the API, DNS lookup for a DNS test now occurs automatically under the following conditions:
- The
dnsServersfield is set to[]. - The
dnsServersfield is set to a user input (custom values that can be specified at deploy time).
A test with validation errors that is included in test template deployment shows an error icon next to the test name. However, when a test with validation errors is not selected for deployment, it was still showing an error icon next to the test name, which could be confusing. This update removes the error icon from appearing when a test is not selected for deployment.
WAN Insights has introduced a new chart showing throughput distribution titled Egress Traffic Distribution. You can find this chart on the Recommendation Detail modal. This chart visually represents the traffic distribution across each available interface (circuit) within your SD-WAN network.
- Policy Verification: Confirm that your configured SD-WAN network policy is actively in effect by viewing the traffic distribution across various interfaces.
- Performance Monitoring: Identify and monitor traffic volume routed through poorly performing interfaces, enabling timely corrective actions.
- Quality and Bandwidth Correlation: Empower your network teams to correlate quality drops on SD-WAN interfaces with throughput data. This is the first step in establishing bandwidth saturation as the root cause of performance issues.
Previously, when a test template already included a DNS test, users still had to provide a DNS server, either manually or using the lookup button in the UI. This extra step added complexity to the test templates process and also created confusion for less experienced users. To ensure a streamlined experience, when a test template includes a DNS test, DNS server information is now looked up automatically. Users can still supply advanced DNS information through global settings.
Users can now choose to omit some tests during test template deployment. Test templates can include tests that are recommended as a best practice. These tests may not be ideal for the given use case. In these situations, users can opt out of including tests that do not fit their deployment scenario. This prevents users from using more units that are necessary and also prevents users from creating extraneous tests that can add overhead. While this feature has already been supported in the API, users deploying test templates through the UI can now de-select any tests they don't wish to deploy.
Users can now search and filter available test templates by name and certification level.
Certification levels on test templates now have improved visibility with template badges that more clearly indicate if a template is certified, partner certified, or a regular user-defined template. This update is part of our new ThousandEyes Google Cloud Platform (GCP) monitoring, created in collaboration with Google Cloud Platform. For more information about our collaboration with Google Cloud Platform, see Get Network Monitoring Visibility Across Your Google Cloud Environments.
We are currently deploying the Endpoint Agent client to RoomOS devices. The update to Control Hub and to devices will be completed for all devices (in the stable release track) by August 22, 2023. To learn how to enable Endpoint Agents on Webex RoomOS devices, see Integration with RoomOS.
The Cisco Secure Client ThousandEyes Endpoint Agent module for Windows will be available on August 22, 2023. The macOS version will be available on September 11, 2023. For instructions on accessing and installing the module, see Secure Client Integration.
Organizations created after July 18, 2023, now have access to the new default alert rules. For existing organizations, ThousandEyes is rolling out this change over the course of the month.
When the new default alert rules are available to your organization, they display in the ThousandEyes platform UI as Default alert rules 2.0. Any new tests that you create will automatically be associated with Default Alert Rules 2.0. Existing tests, which already have the previous set of default alert rules, will remain unchanged.
Additionally, we've designated the severity level for all of these alerts as Minor.
Our dashboards now have a pause option for auto-refreshing. To pause the automatic data refresh, click on the spinning timer located in the dashboard header. Alternatively, you can also pause the auto-refresh by opening the dashboard drill-down component or the widget configuration panel. To resume the auto-refresh, click on the spinning timer again or close either the widget configuration or dashboard drill-down components.
In December, 2022, we updated the Windows Installer to enable the Extended Network Tests feature by default and to include the NPCAP library. Previously, if this option was not selected, and the user had an allowed version of the NPCAP library installed, the agent would not leverage this. We have changed this behavior, and the agent will now utilize the pre-installed NPCAP library (if it is an allowed version). However, in the future, we will only upgrade versions of NPCAP that were originally installed by our installer.
- Resolved an issue wherein some Endpoint Agents didn't run the number of tests permitted by their license type. Now, all Endpoint Agents run the correct number of tests based on their assignments and license permissions.
- Fixed an issue in the dashboard widgets that prevented users from applying the Endpoint Agent filter correctly. Previously, the filter box was broken, and the filter would not allow a downward scroll.
- Fixed an issue in the dashboard widgets where filtered-out locations were incorrectly showing up in the widget results.
Test Templates now show a badge icon for certified templates and partner templates.
- Fixed the invalid JSON error for page load tests with a fixed value for the httpInterval field.
Test templates now automatically perform the DNS lookup, instead of requiring them to be added manually. Users still have the option to add DNS servers manually.
Users now have the ability to drill down from any widget in a dashboard to a specific test view. This is supported for all Cloud and Enterprise Agent tests (except BGP), Endpoint Agent tests, and device data in the platform. For example, when users click on a dashboard widget identifying a spike in latency, a window will open listing all the affected tests; click a test and the test view will open in a new window demonstrating the latency spike for this particular test. This feature will make navigation inside the platform significantly easier and allow for quicker resolution time for our customers. Learn more about this feature in our Troubleshooting with Drill Down article.
On August 16, 2023, we will release the auto-detect feature for Endpoint Scheduled Tests and update the auto-detect behavior for Automated Session Tests (ASTs).
As Endpoints roam from one network to another, they may find some of the test probes are blocked. To combat this, we have launched a new method for our automatic detection. At each network change event, the agent will attempt all three network probe methods - ICMP, TCP SACK, and TCP SYN. The agent will use the probe with the best result. If all probes are equal, the agent will default to TCP SACK.
This enhancement will allow customers to rely more on the auto-configuration and not worry about the changing network conditions a user experiences. Agents must be running an Endpoint Agent with version 1.158.1 or later. TCP tests rely on the extended network tests (formerly called TCP tests) installed. If the agent is missing the extended network tests installation, the agent will continue using ICMP for all tests.
Customers whose automated session tests are set to Auto-detect will automatically shift to this new method on August 16, 2023. Customers with scheduled tests may opt into this new method by changing their probe setting to Auto-detect on August 16.
In 90 days, ThousandEyes will discontinue support for certain IP addresses. The IP addresses that will no longer be supported are:
52.52.142.26
52.52.36.83
If you are currently allowlisting these IP addresses to receive alert notifications, you should continue to do so until October 31, 2023. However, to avoid a hard stop on your incoming ThousandEyes webhooks, we urge you to update your systems to also allow any or all of the following addresses based on your region:
US1 Region
13.56.245.241
52.9.183.148
18.232.232.61
35.168.54.3
107.22.84.44
3.220.243.232
3.218.27.195
3.221.227.188
EU1 Region
18.157.124.37
3.70.3.30
18.156.17.238
18.158.163.183
35.158.19.241
3.127.8.252
46.51.169.205
54.75.173.76
54.217.22.60
34.243.129.225
54.216.15.243
108.128.60.238
After October 31, we strongly advise you remove
52.52.142.26 and 52.52.36.83 from your allow list as we will no longer support them.In approximately 90 days, all IDs for webhook integrations will transition from a numeric value to a string format. This change will be seen on all incoming webhooks across all fields, including but not limited to: Notification ID, Alert Rule ID, Test ID. If you are utilizing custom webhooks, you will need to update ID fields to be enclosed by quotation marks, for example from
"id": {{id}} to "id": "{{id}}". This change will ensure your system can correctly receive and process the new string-based UUIDs. For those of you who deserialize any ID fields as a numeric, or if your webhook receiver cannot otherwise handle a 128-bit string value, we highly 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, necessary adjustments or actions should be taken as soon as possible.As previously announced, in order to support the UUID format in v6 and v7 API endpoints, we have changed the data type of the
alertID from integer to string. These changes have occurred in stages between July 31 and August 3, 2023. For details, see the v6 API reference and the v7 API reference.- Fixed an issue where the top-level timespan in our dashboards was not updating the widget timespans appropriately.
- Resolved an issue where the Endpoint Agent settings in the UI and the associated API calls were incorrectly returning all Endpoint Agents in “View Deleted Agents”. Now, only recoverable agents deleted during the last seven days are returned.
- Fixed a bug where the Endpoint Agent settings no longer showed the System Proxy option after another proxy was selected. The System Proxy option is now always visible as an option.
New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.
- Taipei, Taiwan (FarEastone) (IPv6)
- Paris, France (Free) (IPv6)
Last modified 2d ago