Changelog
You can now configure up to 10 scheduled tests per Endpoint Agent. This higher limit applies to both Endpoint Agent and Endpoint Agent Pulse.
When you edit a transaction script, you can now expand the editor window, for a more ergonomic coding experience.
When you create a report or dashboard widget that uses BGP data and does not use filters, you are now asked to confirm that you want to render the data. This change is made to improve performance when a widget selects a large data set.
This change impacts existing widgets as well as new widgets, but it does not impact existing snapshots.
The following Cloud Agent locations now have IPv6 support:
Mississauga, Canada
Brno, Czech Republic
For a complete list of ThousandEyes Cloud Agent locations, see https://www.thousandeyes.com/product/cloud-agents.
Changing the alert conditions on an existing alert rule inadvertently removed the assigned tests from the alert rule. This issue has been resolved.
In Agent Settings, when you sort the list by Last Contact in ascending order, the list now displays disabled agents last.
An issue sometimes occurred in Internet Insights where the Select All checkboxes in filters could reach a selected state without all options being selected. This issue has been resolved.
In some rare cases, the Endpoint Agent failed to check in when connected over VPN and when a specific HTTP error code had been returned for previous connection requests. This issue has been resolved. With this fix, the Endpoint Agent is now always able to check in when there is a clear Internet connection (VPN or otherwise).
Previously, some transaction tests could time out spuriously on certain agents without any apparent cause. ThousandEyes has determined that the root cause of the issue was variability in certain phases of transaction test setup, and has modified BrowserBot to account for time differently, such that these spurious timeouts cease.
An issue was found where changing the alert conditions on an existing alert rule inadvertently removed all of the assigned tests from the alert rule. This issue has been fixed.
Webhooks using HTTPS endpoints now require that the TLS SNI matches one of the webserver certificate's subject alternative names (SANs). ThousandEyes will reach out to customers that we believe will be directly impacted by this change.
Custom static key-value pairs can now be added to the webhook payload as part of the Alert Key in the Body section of a supported webhook. These custom payloads can only be used on the Cloud or Enterprise Agent alert type, and will be specific to the selected alert rules. This change also adds two new fields to the webhook payload:
testLabels: The test label name and ID.
testTargetsDescription: The description of the test target as defined in the test configuration.
In addition, the Authorization Code grant type has been added to the OAuth workflow for webhooks.
In order to better support Palo Alto and Juniper firewalls in the path visualization, SACK mode can now be enabled for path traces in agent to agent tests.
The Test Table widget has been updated to exclude disabled tests by default. Additionally, a checkbox option has been added to the widget configuration that allows users to include disabled tests in the Test Table widget if needed.
A new button has been added to the script editor in the transaction test settings that will add a sleep command to the transaction script where the cursor is positioned.
An issue occurred when an Endpoint Agent user tried to access a share link immediately after creating it. In some instances, this would result in the user seeing gaps in the data, as they were viewing the share link before all the data had been indexed. This issue has been resolved.
An issue occurred where some Endpoint Agents connected via WiFi showed no wireless information in the Local Networks views. This has been resolved.
Previously, the best-match logic used when searching the Internet Insights catalog on the Catalog Settings page resulted in unexpected results when searching for short terms (for example, ISP). This has been resolved.
When configuring Internet Insights outage alert rules, in some instances, the validation errors did not provide enough information to identify the field that did not validate. This has been resolved.
An issue occurred where many transaction tests would periodically appear to complete successfully (reporting a full waterfall and duration), but end up reporting as having timed out. This was caused by a step in the inter-test setup running over the allocated duration, which counted against the user's configured test timeout time. This has been corrected.
BrowserBot 1.132, which is used by Cloud and Enterprise Agents to conduct page load and transaction tests, includes an upgrade of the te-chromium browser from version 68 to version 80. Users may observe changes in test behavior due to the browser upgrade.
Red Hat Enterprise Linux and CentOS environments now require java-1.8.0-openjdk rather than java-1.7..0-openjdk.
Debian-based agents are not affected by this update as they already use java-1.8.0-openjdk.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To assist with managing your end-user experience, ThousandEyes is offering free access to our End User Monitoring until July 31, 2020. If this is of interest to you, reach out soon — enrollment for this offer ends on June 30, 2020. For more information, please see our blog or contact the ThousandEyes team.
The default BGP alert rule has been updated to fire when 10% of monitors have less than 100% reachability.
Note: This change will be applied moving forward and retroactively, but will only impact the default BGP alert rules that have not been updated by a customer.
Note: These changes will occur in sequence; initially, the change will be made for new rules, and then in the next couple of weeks, the changes will be made retroactively.
Transaction scripts can now contain up to 200 defined markers.
The Waterfall tab now includes a Show More link for when there are more than 10 markers to display.
Internet Insights
The number and ID of affected tests reported in outage alerts are now available via the alerts API. See v7 API documentation.
Added more specific tooltip titles to the metrics displayed in the timeline for Endpoint Agent local networks.
An issue occurred with the v7 Dashboard API that was allowing users to create, update, or delete dashboards using the GET method instead of the appropriate HTTP method POST. This has been fixed.
An issue was found where gaps could appear between the page bars shown in the Waterfall view when browser-based tests targeted certain pages. This was caused by missing start/end time requests for those pages, and has been resolved.
An issue occurred where transaction tests would periodically appear to complete successfully (reporting a full waterfall and duration), but would also report as having timed out. This was caused by part of the inter-test setup overrunning its allocated duration, and counting against the user's configured test timeout. This has been resolved.
An error occurred when transaction scripts that used the waitForDownload() function were configured to use an HTTP proxy. In these circumstances, the test would fail. This was caused by the way waitForDownload() had been implemented, and has been resolved.
An error occurred when transaction scripts were configured to use an HTTP proxy where the proxy would receive periodic HTTP requests on port 9999 that were not intended to leave the agent. This was caused by the way the waitForDownload() function had been implemented, and has been resolved.
Previously, the outage swimlane tooltip would sometimes cover the Internet Insights Views timeline selection, making it difficult to click on the timeline. The tooltip positioning has been changed and the issue is now resolved.
An issue occurred that required users to have the View alert rules permission in order to view the Endpoint Agent Views and Test Settings pages. This has been resolved.
An issue occurred where agents remained disabled after a customer's trial period was extended. This has been corrected.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To assist with managing your end-user experience, ThousandEyes is offering free access to our End User Monitoring until July 31, 2020. If this is of interest to you, reach out soon — enrollment for this offer ends on June 30, 2020. For more information, please see our blog or contact the ThousandEyes team.
Previously, the scheduled tests assigned to an agent were randomly selected from the list of pre-assigned tests. Now, tests containing a label that matches specifically to an agent are prioritized ahead of all other tests when they are assigned execution slots.
The URL and network target can now be edited in the Scheduled Test Settings form when you edit a test.
Reachable VPN nodes are now displayed on the path visualizations created for scheduled tests.
Endpoint Agent browser session alerts are now supported in the Alert Grid and Alert List widgets.
An issue occurred where the Markers filter was showing duplicate markers if a saved event shared the same name as the test it was created from. This duplication has been resolved.
An issue occurred that caused public dashboards and reports to be deleted when the original creator was deleted from the platform. Dashboards and reports now remain within the appropriate account group even when a user is deleted.
An issue caused embedded links to be deleted when a user updated a dashboard or a report through the API. This has been resolved.
In some instances, the Download button for report snapshots was grayed out and non-functional. This has been resolved.
An issue in the registration process caused the process to abort when it encountered network errors. This has been resolved.
The Headers link was missing under the Response code column in the Table view for Endpoint Agent HTTP server tests. It is now displayed correctly.
An issue sometimes occurred where the Affected Tests filter in Internet Insights would display a "loading" animation indefinitely and the test list would never complete loading. This issue has been resolved.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To assist with managing your end-user experience, ThousandEyes is offering free access to our End User Monitoring until July 31, 2020. If this is of interest to you, reach out soon — enrollment for this offer ends on June 30, 2020. For more information, please see our blog or contact the ThousandEyes team.
ThousandEyes has expanded our Enterprise Agent deployment options to include support for Raspberry Pi 4. A new download option is now available, along with installation instructions, on the Agent Settings page.
Browser-based tests are not supported when running an Enterprise Agent on Raspberry Pi 4.
Updated Agent Statistics Tab
The Agent Statistics tab in the Agent Settings view has been revamped to provide per test contribution to agent utilization. The tab now includes the host account group, test type, average utilization, and max utilization of each test to provide greater context.
In addition, agent uptime and utilization metrics are available over a longer time period (up to 30 days).
The location filter on the Internet Insights Views page has been updated. Locations are now grouped by area and country, allowing users to search more effectively.
ThousandEyes has added a new Cloud Agent with IPv6 capabilities in Buenos Aires. For a complete list of our Cloud Agent locations, see https://www.thousandeyes.com/product/cloud-agents.
ThousandEyes is deprecating the voice call test type on August 31, 2020.
Voice call tests simulate a full Voice over Internet Protocol (VoIP) call sequence, starting with the session initiation using the Session Initiation Protocol (SIP), and then the voice data transmission using the Real-time Transport Protocol (RTP) between one or more ThousandEyes agents and a target agent, acting as the VoIP user agents (or the call endpoints).
A voice call test can be migrated to separate SIP and RTP tests without incurring additional unit consumption. For more information about SIP and RTP test configuration, see SIP Server Test Settings and RTP Stream Test Settings. Contact support for more information.
An issue occurred where device views would become unresponsive when navigating from the Alerts List page, or from alert notification emails. This has been resolved.
Under certain conditions, the certification path displayed was not the certification path used by the test's TLS connection. The way the certificate chain is shown in the Response Details panel has been changed to show the more commonly used certificate chain in the case of cross-signed certificates.
An issue in the Test Settings page was found where the bypass list configured in proxy settings would bleed across the test settings box if there were greater than 4 entries. This has been resolved.
An issue was found in Device views where the "interface" filter selection did not auto-populate all available options a user would typically be able to select. This has been fixed.
An issue occurred where inconsistent times were displayed on report widgets based on the users timezone. This has been updated to accurately reflect the time regardless of timezone.
In rare production circumstances, a previously identified and fixed issue that resulted in a report snapshot being emailed twice instead of once would reappear. Additional checks have been added to ensure the issue is now resolved.
An issue with test table widgets existed where user-created labels were not showing up as filterable options. This has been corrected.
The color grid widget filter option was not working properly, and has been fixed.
An issue occurred where the filter values selector for individual widgets was enabled before a metric was selected. The filter values selector is now only available when a metric has been selected.
An error occurred that resulted in an agent being displayed multiple times in a filter. This has been resolved.
An issue occurred where Endpoint Agents without data reported as 100% data loss in dashboards. This has been resolved.
A race condition prevented setting changes from being applied to some Endpoint Agent tests. This has been resolved.
An issue occurred where changing the Endpoint Agent network topology view grouping could cause the web UI to hang. This has been resolved.
An error occurred when clicking the "Show Network Topology of this Agent" link for an Endpoint Agent that resulted in a perpetual loading icon. This has been resolved.
An issue occurred where an error was displayed when attempting to modify a label. This has been fixed.
We have resolved an issue in Internet Insights where in some cases, when creating an outage alert rule, the "Catalog Providers" dropdown menu had a blank entry.
An issue causing animations on the Internet Insights Overview page to occasionally consume 100% CPU has been resolved.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To assist with managing your end-user experience, ThousandEyes is offering free access to our End User Monitoring until July 31, 2020. If this is of interest to you, reach out soon — enrollment for this offer ends on June 30, 2020. For more information, please see our blog or contact the ThousandEyes team.
Browser-based tests have been reverted to Chromium 68 due to issues found during the deployment of Chromium 80.
Transaction (Classic) Test Migration Workflow
ThousandEyes has built a test conversion workflow to support migrating transaction (classic) tests to the new transaction test type. This workflow will be rolled out to customers with existing transaction (classic) tests over the coming weeks, and will be accessible from the Test Settings view.
Transaction (classic) tests that need to be migrated are marked with a warning icon. To use the test conversion workflow, select the test to expand the window, and click the Migrate Test button:
Clicking the button will navigate users to a Test Settings view populated with an auto-generated configuration for an equivalent transaction test. The user can then inspect the script, run an instant test to validate the migrated script, make any necessary changes, and save the new test.
Updated Agent Settings View
The types of tests with the highest agent utilization are now visible on the Agent Settings view to provide additional clarity to users. Hover the cursor over the utilization metric to see detailed metrics across other test types and hyperlinks to our documentation that explains agent utilization in more detail.
Internal top-level domains (for example, .local or .corp) are now supported in browser sessions.
Multiple trace routes are now shown for local network paths.
Private subnet mask information is now displayed in the Session Details tab.
The Internet Insights catalog now includes coverage of the following providers:
IaaS: Alibaba Cloud, IBM Cloud, Google/GCP (updated)
ISP: 2PIFI (CyrusOne)
CDN: AWS CloudFront
DNS: AWS Route53
UCaaS: Microsoft Teams
SECaaS: Radware
Logged-in Internet Insights users can now click through from a snapshot affected by an outage to the outage event in Internet Insights.
Previously, in instances where a path trace was performed on an agent-to-agent test, if the path trace target was behind a network address translation (NAT) and the NAT traversal failed, the path trace would throw an error and not collect any data.
Path trace will now be performed on the public IP address of the target agent if the NAT traversal fails, using the port configured in agent-to-agent test settings.
We are now deprecating the use of TLS 1.1 on ThousandEyes infrastructure. After May 13th, 2020, clients that only use TLS 1.1 will not be able to access web resources.
Previously, customers would receive a 400 error code if they attempted to create a snapshot of transaction test data through the /v6/snapshot.json API endpoint. This has been resolved.
An issue was found where an embedded color grid widget wouldn’t show color cards that had a value of 0. This has been resolved.
An issue was found where the grouped bar chart widget sub-header was incorrectly showing \ . This has been fixed.
An issue was found where the map widget test filter was incorrectly showing all test types instead of the test types of the selected data source. This has been resolved.
An issue occurred where an error message would be displayed when an AnyConnect VPN was queried by the Endpoint Agent, if the VPN was active and configured to be used in "Start Before Logon" mode. This has been resolved.
An issue occured where network tests would occasionally fail after a machine woke from sleep. This has been fixed.
Occasional, intermittent gaps were observed for some Endpoint Agents running scheduled tests. This issue has been resolved.
An issue occurred where DNS information was lost on the Local Networks view when navigating through the timeline. This has been fixed.
Formatting issues with the window title of the traceroute style output in Endpoint Agent scheduled tests were resolved.
An issue occurred where the error totals displayed on the Browser Sessions page were including network errors. This has been corrected.
The wording of the affected interface node hover state has been improved to clarify that the tests displayed after clicking the "Affected Tests" link belong to the customer.
An issue occurred where the outage event swimlane and tooltip were not displayed in Internet Insights share links when the affected test metric was selected. This has been resolved.
An issue sometimes occurred where the topology would not display if a user repeatedly double-clicked the "Next nodes" link in Views. This has been corrected.
Previously, when an outage was filtered from the Timeline view, the outage topology would sometimes be incorrectly displayed. This has been resolved.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To assist with managing your end-user experience, ThousandEyes is offering free access to our End User Monitoring until July 31, 2020. If this is of interest to you, reach out soon — enrollment for this offer ends on June 30, 2020. For more information, please see our blog or contact the ThousandEyes team.
In the next release, ThousandEyes will be disabling the ability to create additional transaction (Classic) tests from the product.
ThousandEyes will be working with individual customers as well as making an automated conversion process from within the product console available to assist with the migration process. This tool is expected to be available in May. If you need the ability to create additional transaction (Classic) tests after April 30, contact the ThousandEyes support team.
ThousandEyes is excited to announce the launch of our new website for product documentation. This is the first stage in our efforts to provide users with an improved content experience.
The documentation site can be found at docs.thousandeyes.com. For more information, see the ThousandEyes Blog.
TLS Certificate Expiration and Session Information
ThousandEyes has introduced the ability to alert on certificate expiration and TLS session information. All existing and new HTTP server tests will now include TLS session information such as the certificate chain, TLS version, and cipher suite negotiated in a new slide-out modal that will also include HTTP request and response headers:
In addition to being able to view TLS session information in HTTP Server view, customers can configure alerts for the following new associated metrics:
Certificate expiration
TLS version
Weaker Cipher Suite negotiated
For more information, see our TLS Certificates blog.
Certificate chain and session information have also been added to the /v6/web/http-server/{testID}?certificates=1 endpoint. Example output is shown below:
"sslVersion": "TLSv1.2","sslCipher": "ECDHE-RSA-AES128-GCM-SHA256","sslCerts": [{"notValidAfter": "2020-06-03 12:00:00","notValidBefore": "2018-05-08 00:00:00","subjectName": "github.com","issuerName": "DigiCert SHA2 Extended Validation Server CA","subjectAltNames": ["github.com","www.github.com"],"fetchDateInValidCertDateRange": true,"daysUntilExpiry": 35}
See the developer documentation for more information.
White Node Collapsing in Path Visualization
To improve path visualization page performance, instances with three or more consecutive white (star nodes) in the path visualization will be collapsed into a group by default.
Collapsed white nodes:
Expanded path visualization after clicking on the grouped number:
Pagination has been added to the dashboard “Test Table” widget.
The “Shared” dashboard label has been renamed “Shared with others” for dashboards shared across account groups.
Browser-based tests have been upgraded from Chromium 68 to Chromium 80.
Forwarding loss can now be shown within Endpoint Agent path trace views.
Important: This enhancement will be available with the next Client release (currently estimated for May 4th).
The Agent Settings page is now paginated to improve usability when managing large numbers of Endpoint Agents.
Added a welcome page to help customers get started with Internet Insights:
For subscribers: The content covers key concepts, product areas, and links to existing resources and can be re-launched from the Help menu.
For non-subscribers: The Internet Insights navigation menu link now directs users to in-product content instead of opening the product offering page in a new tab.
Internet Insights outage alerts are now available via the ThousandEyes v7 API. See the v7 API documentation available at https://developer.thousandeyes.com/v7/ for details.
Internet Insights outage alert rule names can now be edited.
The Internet Insights destination network filter has been renamed from "Network" to "Destination Network" in order to make it easier to distinguish from the affected interfaces network filter.
Alerts
The ThousandEyes v7 API (preview) now includes the an alerts endpoint. For more information, see the developer documentation.
Endpoint Agent
The last seen IP address of an Endpoint Agent is now available via the API.
The Endpoint Agent’s name can now be updated via the API.
The username associated with an Endpoint Agent is now available via the API.
ThousandEyes has made a change to the Sharing section that lists the Snapshots and Saved Events available. Specifically, we removed the 'Shared with Me' from the Snapshots, as many customers found it confusing to see snapshots that were shared with members of an organization account, in addition to those that were shared with the individual administrator.
The ThousandEyes mobile cloud agents introduced in January will be taken offline for the near future in order to make architectural changes that will ensure we provide the best quality data on the optimum networks.
The following agents will be removed on April 30, 2020:
Chicago, IL (AT&T Mobile), (T-Mobile), or (Verizon Mobile)
New York, NY (AT&T Mobile), (T-Mobile), or (Verizon Mobile)
Dallas, TX (AT&T Mobile), (T-Mobile), or (Verizon Mobile)
Los Angeles, CA (AT&T Mobile), (T-Mobile), or (Verizon Mobile)
San Jose, CA (AT&T Mobile), (T-Mobile), or (Verizon Mobile)
Transaction tests no longer support Adobe Flash-based user workflows.
An issue occurred where there was a difference between the time shown in the dashboard test table widget when compared to the Test view. This was caused by the widget using UTC rather than the local user time, and has been resolved.
In rare instances, an issue occurred where a report snapshot was emailed twice instead of once. This has been resolved.
An issue occurred where the "location" filter for Endpoint Agents was presenting either incorrect options or no options at all. This has been fixed.
Previously, some customers were unable to run Transaction tests on some Enterprise Agents because another process was binding to port 53 on a network interface created by te-sandboxd. A "warn"-level log will now appear in te-sandboxd when this configuration is detected.
Previously, Transaction tests were not able to perform downloads.waitForDownload() commands in a test that is configured to use an HTTP proxy. This has been resolved.
Previously, some snapshots of browser-based test data were taking longer than an hour to process. This has been resolved.
Previously, in Transaction test views, very long marker names could cause their corresponding durations to appear in the wrong place. Layout and styling adjustments have been made to resolve this error.
An issue occurred where several data points were missing or empty when connecting via a Cisco AnyConnect VPN. This has been resolved.
Fixed an issue that resulted in an "account mismatch" check misfiring during uninstalls.
An issue occurred where an instant test would show “Loading” forever if agents were submitting data, but not for the selected metric. This has been resolved.
An error caused the support chat window to be hidden in some views. This has been fixed.
An error was caused by the Endpoint Agent link speed being inconsistently calculated. This has been resolved.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To help with the increased surge of remote workers, we at ThousandEyes are offering our Endpoint Agent product, free of charge. For more information, please see our blog or contact the ThousandEyes team.
In the next release, ThousandEyes will be disabling the ability to create additional transaction (Classic) tests from the product.
ThousandEyes will be working with individual customers as well as making an automated conversion process from within the product console available to assist with the migration process. This tool is expected to be available in May. If you need the ability to create additional transaction (Classic) tests after April 30, contact the ThousandEyes support team.
ThousandEyes now supports installing Enterprise Agents on Amazon Linux 2 operating systems.
ThousandEyes is excited to announce that at the end of April, we will be launching a new website for product documentation. This is the first stage in our efforts to provide users with an improved content experience.
The new “sticky agent” feature allows a user to configure alerts that only trigger when the same agent/s meet a specific condition in any number of consecutive rounds.
For example, an alert rule is configured for if the same agent trips a specified threshold in three consecutive rounds. The Atlanta cloud agent trips the rule in round one, the Ashburn cloud agent trips it in round two, and the San Francisco cloud agent trips it in rule three.
In this scenario, the alert rule would not trigger when using sticky agents. Either Atlanta, Ashburn, or San Francisco would need to trip the rule in three consecutive rounds to trigger the alert.
This can be used to configure alerts about the health of the network in a specific agent’s location, to increase confidence in the accuracy of alerts being sent (for example, issues that are seen from the same set of agents across multiple rounds), or to improve the signal to noise ratio by reporting on agent health as opposed to only test health.
For more information, see How Alerts Work.
Improved the warning message that notifies users when an agent set is mixed, as bandwidth measurements are not allowed to run from Cloud Agents.
The Endpoint agent now supports Microsoft Edge version 79 or higher for collecting browser session metrics. To install the extension:
On the desired endpoint, launch Microsoft Edge.
Open the following link: https://app.thousandeyes.com/install/endpoint-agent
The createdTime, lastSeen and version fields are now exposed in the /endpoint-agents API.
Several improvements have been made to how Internet Insights displays outages. Outage event metrics (begin, end, and duration) have been added in the following areas of the UI:
Views:
A purple outage swimlane has been added below the timeline to improve visibility of long outages and outages that cross a five-minute period.
A tooltip appears when hovering over events on the swimlane, improving discoverability of individual outages and of when multiple outages occur at the same time.
Views > Topology:
In the text displayed while hovering over an affected interface node, a list of outages is now displayed when multiple outages occur at the same time.
Views > Table:
Outage event metrics have been added to the Table view.
In some instances, an issue occurred when a transaction script failed for a reason other than a test timeout that resulted in the error not being reported correctly. This has now been resolved, and detailed error messages should be seen for all failed transaction scripts.
Previously, there was no option in Transaction test settings to enable following redirects in the HTTP server layer of the test. This has been corrected.
Fixed an issue that only allowed Latin1 characters in the post body; all UTF-8 characters are now allowed
Fuzzy searching in the agent selector in test settings has been disabled due to unexpected results.
DNS Server snapshots that had a server selected were producing an incorrect "Invalid URL parameters" popup. This has been corrected.
The link to the "Getting Started" videos in the Help & Support dropdown was not loading correctly. This has been fixed.
Previously, creating a test with a duplicate test name failed with no feedback. The intended error message has been restored.
An issue occurred when highlighted controls in the Device Topology view were not updating when the selected metric was changed. This has been fixed.
An issue occurred where organizations with large numbers of Endpoint Agents could not use labels to correctly filter their data in dashboards and reports. This has been resolved.
Previously, the AlertList widget included DNS+ alerts, but the AlertGrid widget does not. This lead to inconsistencies when looking between the two widgets. DNS+ alerts are now available in the AlertGrid widget.
Endpoint Agent links inside the map widget were incorrectly pointing to the Enterprise Agent list. This has been resolved.
An issue occurred when too much data resulted in the browser being unable to render the Path Visualization. This following corrections have been made to resolve this issue:
The error message displayed in the UI has been corrected, and now states “The path trace graph is too big, try adding some filters.”
The default grouping has been set to “Agents” in all Endpoint Agent view scenarios.
An issue occurred where Path visualization controllers ( Filter, Group By, and Number of hops etc) were not displayed when there was too much data. This has been resolved.
An issue occurred in the network topology where trying to apply any filter would result in a spinning wheel and not return any options. This is now fixed.
An issue that caused the agent label color to revert to gray when the name was edited has been corrected.
Previously, the Verify Content checkbox stayed enabled after removing specified content when setting up a new test. This is now fixed.
An issue occurred with some path visualization filters where search options were filtered out and not displayed as they were not on the current pagination page. This issue has been fixed.
An issue when creating / modifying a test resulted in the custom user agent string disappearing from the UI after saving. This has been fixed.
The support chat window was not visible on the Endpoint Agents → Overview page. This has been corrected.
An issue occurred with the Internet Explorer extension where hovering over an element in the browser session waterfall displayed the HTTP method as UNKNOWN. An error message to show that headers for the IE extension are not supported.
A recent change to the user profile created during registration allowed non UTF-8 characters to be used in a username, causing the username to fail to register. This has been corrected, and only valid UTF-8 characters can now be submitted.
An error occurred when opening some share links where an incorrect popup error would occur. This has been fixed.
An issue occurred where clicking the gear icon next to a scheduled test did not filter and expand the scheduled test settings panel. This has been resolved.
Fixed an issue where Endpoint Agents with connection failures were not showing a severity color.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To help with the increased surge of remote workers, we at ThousandEyes are offering our Endpoint Agent product, free of charge. For more information, please see our blog or contact the ThousandEyes team.
In the next ThousandEyes release, the Alerts API endpoint will be updated to version 7.
The ThousandEyes API version 7 is currently in preview mode. As this version is subject to change, ThousandEyes recommends customers that are using version 7 revert back to the stable v6 API as soon as possible, unless accessing APIv7-specific endpoints that are not available in v6.
In the coming weeks, ThousandEyes will be starting a migration plan to help customers migrate their existing transaction (classic) tests to the transaction test type. As part of that migration plan, we will be disabling the ability to create additional transaction (classic) tests from the product on April 30.
ThousandEyes will be working with individual customers as well as making an automated conversion tool available in the coming months to assist with the migration. If you need the ability to create additional transaction (classic) tests after April 30, contact the ThousandEyes support team.
In an upcoming release, ThousandEyes will upgrade the version of Chromium used by browser-based tests (page load, transaction [classic], and transaction tests) from version 68 to version 79. As part of this upgrade, Flash will no longer be supported, and any page load, transaction (classic), or Transaction test that depends on Flash is unlikely to continue working.
As of this release, new customers will be required to deploy enterprise agents on Red Hat Enterprise Linux and CentOS versions 7.6 and later. RHEL and CentOS versions 7.4 and 7.5 have now been placed in the end of support lifecycle. ThousandEyes will be reaching out to customers to ensure there is time to upgrade.
Note: For more information on the end of support lifecycle, see Enterprise Agent support lifecycle policy.
ThousandEyes recommends that customers upgrade to the latest RHEL 7 minor version (version 7.7).
Warning: Red Hat Enterprise Linux 8 is not currently supported. Do not upgrade to RHEL 8.x.
ThousandEyes is excited to announce that we will soon be launching a new website for product documentation. This is the first stage in our efforts to provide users with an improved content experience.
More information will be included in future release notes as we get closer to launch.
ThousandEyes has added a new Cloud Agent with IPv6 capabilities in Panamá City. For a complete list of our Cloud Agent locations, see https://www.thousandeyes.com/product/cloud-agents.
Previously, reports and dashboards that were shared across account groups were tagged as “Shared by Me”. This has been updated to “Shared”.
In previous releases, editing the direction for Agent to Agent alert rules was not possible. This has now been corrected, and the direction can now be configured.
An issue occurred for some Enterprise Agent users where BrowserBot was attempting to reuse Chromium browsers across multiple test rounds, and not resetting Chromium’s connection pools. This resulted in inconsistent transaction test results, and has been resolved.
Previously, XmlHttpRequests (“fetch()” requests, asynchronous HTTP requests, or XHR requests) requests that occurred during page load or transaction tests were not collected by BrowserBot, and not displayed in the waterfall view. This has been corrected.
An issue occurred when users selected or deselected credentials in the transaction test settings view, where unrelated credentials could toggle as well. This has been resolved.
Previously, network timings for assets were listed in the API v6 as -1 if the timing datum was not available (for example, if the assets were loaded from the browser’s cache), without context for the value. The API v6 has been updated to indicate on a per-asset basis whether the asset was loaded from the cache, to avoid confusion.
An inconsistency existed between the timeline and error breakdown for HTTP server views. This was because the timeline used time to first byte (TTFB) errors for the availability metric, while the error breakdown did not. TTFB errors have been removed from the availability metric calculation to correct this inconsistency.
Previously, the Agent Selector was missing from the "Run now → With changes" Views menu. This has been fixed.
Previously, public monitors could not be filtered during widget configuration when building a BGP-specific report or dashboard. This has been corrected, and public monitors can now be filtered as expected.
An issue occurred that prevented some users from duplicating a ThousandEyes built-in report. All reports can now be duplicated as expected.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To help with the increased surge of remote workers, we at ThousandEyes are offering our Endpoint Agent product, free of charge. For more information, please see our blog or contact the ThousandEyes team.
ThousandEyes is pleased to announce the release of status.thousandeyes.com.
status.thousandeyes.com is a unified service for monitoring health statistics, viewing announcements, and managing notification subscriptions. ThousandEyes platform and Cloud Agent announcements, traditionally posted at success.thousandeyes.com, will now be posted at status.thousandeyes.com.
Users may now choose from email, SMS, or RSS notification. Due to new subscription options, all previous notification subscriptions will not be carried over to this new service. We encourage users to sign up and select their preferred notification options as soon as possible. Notifications from our legacy platform will be discontinued on April 30th.
Our support team is available to answer any questions via our in-application chat or support@thousandeyes.com.
In an upcoming release, ThousandEyes will upgrade the version of Chromium used by browser-based tests (page load, transaction [classic], and transaction tests) from version 68 to version 79. As part of this upgrade, Flash will no longer be supported, and any page load, transaction (classic), or transaction test that depends on Flash is unlikely to continue working.
For users who are implementing SD-WAN at their branches, a key need is the ability to measure performance across each WAN circuit. Currently, SD-WAN policies determine which WAN circuit is preferred for traffic that originates from the agent. Allowing the ability to select the interface and IP address for agent traffic allows users to direct agent traffic to across a particular WAN circuit.
You can now configure additional network interfaces for the ThousandEyes Virtual Appliance, and select which interface should be used for each test. Alternatively, you can also configure additional IP addresses for an existing interface. For a detailed guide, see this ThousandEyes Knowledge Base article.
To configure which interface should be used for a test, go to Cloud & Enterprise Agents > Test Settings:
For Endpoint Agents, you can now configure alerts to be triggered based on system metrics (CPU and memory). These system-metrics alerts are included in the Alert List page and in notifications in the same way as other alert types.
Transaction script users can now use import net from 'thousandeyes', in order to take advantage of the helper methods connect(port, host) and connectTls(port, host, options) for forming raw TCP and TLS connections, respectively.
Note that these methods return promisified sockets, allowing users to await on method calls for sending and receiving bytes. Previously, users had to follow a clumsy process of registering and deregistering callbacks from a standard Node.js socket.
ThousandEyes has improved the way agents are displayed and organized in the Topology view. This change introduces three new agent grouping options:
Origin Network - Groups agents by their origin network.
Next Hop Network - Groups agents by the network in the next hop.
Agent - Lists agents (sorted by the number of affected tests).
If Internet Insights does not have enough information about an agent to display details, it includes that agent in the Other Networks grouping.
In certain customer environments, middleboxes like Palo Alto and Juniper firewalls interfere with the way the ThousandEyes platform collects path trace metrics, leading to incomplete path information. In order to better support such scenarios, ThousandEyes has added the capability to perform path trace "in session", which first initiates a TCP session with the target server and sends path trace packets within that TCP session. For tests with Network metrics, the new option is configured in the Advanced Settings of the test, using the Path Trace Mode setting. Select the In Session checkbox:
This capability has been added to the ThousandEyes API as well, in a new test object field called pathTraceMode.
Slack integrations used the default Slack channel, rather than the one specified in the configuration. The system has now been changed so that it now sends alerts to the specified channel.
In the Recorder IDE, when you click Insert Markers, the system now inserts a markers.start( )…markers.stop( ) block, instead of a call to markers.set( ). The new block is designed to clarify the start/stop nature of the calls. markers.set( ) is still supported as before.
A bug has been fixed that caused the Box-and-Whiskers widget to display incorrect data.
On the Dashboards page, the Alert List widget was not automatically updating the relative start time of active alerts when the dashboard was refreshed.
On Windows, the Chrome browser extension component of Endpoint Agent in some cases incorrectly reported a status of inactive. ThousandEyes has fixed this issue by more accurately determining the extension's status: rather than being based on installation alone, the extension's status is now based on whether it is communicating with the backend.
An issue has been fixed that prevented the transfer of disabled tests to a different account group if an organization was close to its usage limit.
The COVID-19 virus is putting a huge strain on IT and network teams all around the world. To help with the increased surge of remote workers, we at ThousandEyes are offering our Endpoint Agent product, free of charge. For more information, please see our blog or contact the ThousandEyes team.
In an upcoming release, ThousandEyes will upgrade the version of Chromium used by browser-based tests (Page Load, Transaction [Classic], and Transaction tests) from version 68 to version 79. As part of this upgrade, Flash will no longer be supported, and any Page Load, Transaction (Classic), or Transaction test that depends on Flash is unlikely to continue working.
When you create a report or a dashboard, you can now exclude data that was captured during a configured alert suppression window. This change should improve the reliability of ThousandEyes reports and dashboards, as they will not include data on planned downtime or maintenance windows.
The Reports page now includes the Color Grid widget. This widget has identical functionality to that of the Color Grid widget found in the Dashboards page.
The message that the Alert List widget displays when there are no active alerts has been updated from No Data to No Alert Activity. The previous message implied that the account had never had any alerts; the new message indicates that there are currently no alerts.
On the Overview page, the default time range is now 60 minutes. The previous default range was 10 minutes, which led to confusion if there was no data within that period. With a longer default range, you should more easily see the overall health of your users’ experience.
On the Usage and Billing page, projections have been updated and should no longer result in discrepancies when compared to the Test Settings page.
As announced earlier, ThousandEyes has ended support for alert notifications with HipChat. The ThousandEyes Support team has worked with affected customers, and HipChat integrations have been removed.
In order to better support tests that have a large number of traces, the Path Visualization view now uses a different method for pagination. Pagination is now based on the total number of traces in the visualization, rather than on the number of source agents. The new pagination provides faster rendering of the Path Visualization.
When an alert notification included a link to see a BGP test view, the link resulted in the following error:
The given server isn’t valid for the current state.The error has been resolved.
On the Reports page, when data in the table widget was grouped by agent label, an empty column was created. This issue has been fixed.
When an agent label was deleted, tests that were attached to that label could not be enabled or disabled with the Enabled checkbox. You can now enable and disable these tests
Once a year, our entire company gathers together in the San Francisco Bay Area in order to set the organization's priorities and cadence for the year that follows. This year, the event will occur during the week of March 1st, 2020.
In order to allow all team members to participate, our chat and telephone-based support hours will be reduced to 12 hours per day, from 6am to 6pm Pacific Standard Time, starting Sunday March 1st. We'll still have a team on call during the off-hours, but will be operating with reduced response times. We will resume 24-hour coverage beginning on March 8th.
See this article for more information, or contact either your account manager or our support team.
ThousandEyes users can now monitor and interact with arbitrary API endpoints from within a transaction script (for example, making HTTP requests and initiating TCP and TLS connections directly from the transaction scripts’ execution environment). This allows users to implement transaction testing in a number of new ways, including:
Surrounding a fetch HTTP request with markers to measure the responsiveness of an API endpoint.
Testing arbitrary and proprietary network protocols.
Making POST calls directly to an API endpoint.
Mixing API calls and browser commands to, for example, create a resource via API and then view its data through the web application's frontend.
Using an API endpoint to generate an ephemeral access token for use in a transaction test.
New Endpoint Agent labels can now be created when running an Instant Test with additional changes.
From the Test view, open the Run Now drop-down menu and click With changes.
Open the Agent Label dropdown menu.
Click Create New Label.
The Add New Label panel will now open.
The Developer API now exposes the ability to create, run, and re-run Endpoint Agent Instant Tests. In addition, users can list the existing set of Endpoint Agent labels, as well as create new ones.
In early March, ThousandEyes is ending support for alert notifications with HipChat. The ThousandEyes Support team will be reaching out to customers that use the integration, to assist with transitioning to other notification channels.
Previously, customers were unable to select or copy the text of the Target URL visible in browser-based test views. This issue has been fixed.
An issue occurred when viewing transaction test data, where timeline marker selections could be reset when selecting a different set of agents, or by changing between test layers. Marker selection stickiness has been improved to resolve this issue.
A change to te-sandboxd prevented Red Hat Enterprise Linux (RHEL) agents from running transaction tests. This was the result of RHEL-specific behavior that caused a filesystem to be mounted with insufficient permissions. Customers running te-browserbot version 1.116 or later should no longer experience this issue.
An issue occurred when customers ran page load or transaction tests on sites that made asynchronous HTTP requests, that resulted in BrowserBot failing to detect and collect those requests. This caused the tests to be omitted from the waterfall test view. The issue has been resolved.
For some categories of transaction test failures, BrowserBot would fail to collect a browser final screenshot. This issue has been resolved.
An issue would sometimes occur where the table view for transaction test data would contain a row that simultaneously said “zero errors” and showed no error icon, but had no entry for “transaction time”. This was caused by a UI rendering bug, and both tests and errors now display correctly.
Previously, the ThousandEyes API for transaction tests returned broken links for network metrics and for path visualization. The correct links are now returned.
Issues were found in the UI design for the transaction waterfall view that resulted in the view becoming illegible or unusable in certain circumstances. The design has been refined, and these issues should no longer occur.
Previously, NTLM was not selectable in the settings for the HTTP server portion of a transaction test. This has been corrected.
When configuring the Color Grid widget, if the SIP Availability metric was selected, the tile colors would not accurately affect the color scale selections. This has been fixed, and the tile colors now display as expected.
A visual error resulted in tests using agents in Hong Kong and Singapore not highlighting the two countries correctly in the Geomap widget. This has been resolved.
An issue occurred where Endpoint Agent cached objects were marked as “Object incomplete” as they did not have content size information. This has now been resolved.
An issue with authentication tokens resulted in Endpoint Agent shared links not working for newly created accounts. This was caused by the token not being generated upon account creation, resulting in potential race conditions that impacted the share links. Tokens are now generated upon account creation, resolving the issue.
An error occurred that prevented color changes to Endpoint Agent labels from being saved if the color was the only change made. This has now been resolved.
ThousandEyes has updated the Topology view to improve how destination interfaces are displayed and organized. A new IP Prefix grouping option has been added. This allows users to filter the Destination view, so that only nodes with IP prefixes are shown.
In addition, nodes that do not have enough information to display are now grouped as “Other Destination(s)” in the Topology view.
Endpoint Agent users can now trigger instant tests, allowing them to run one-time queries, validate test configuration, and troubleshoot problems, without waiting for a scheduled test to run.
System metrics are now included in Endpoint Agent scheduled tests, network tests, and browser sessions. These metrics (including CPU load and memory consumption) provide a more comprehensive overview of the state of the end-user’s machine when the test was run, allowing for a clearer understanding of test results and data.
The ThousandEyes API (version 7) now includes the new Dashboard API. Users can create, update, delete, and read dashboards, as well as retrieve data from dashboard widgets. For more information, see the Developer documentation.
In early March, ThousandEyes is ending support for alert notifications with HipChat. The ThousandEyes Support team will be reaching out to customers that use the integration, to assist with transitioning to other notification channels.
A change in authentication requirements resulted in the ThousandEyes Virtual Appliance (TEVA) diagnostics page displaying a warning that the ThousandEyes collector was unreachable, despite it working as expected. This error has been resolved.
An error occurred during some new Endpoint Agent installations, resulting in the following error message:
“Recording is not enabled for this page at this time on Endpoint Agent”This was caused by an issue with how monitored networks were configured and has been corrected. The Endpoint Agent Extension is now able to initiate recordings before setting up monitored networks.
An issue occurred in the Proxy Settings tab, where a user’s configuration changes were not fully rolled back after clicking Cancel. This has been resolved.