Release Notes: 2017-10-25
Last updated
Last updated
Welcome to a major new feature release!
Before the big new news, some quick announcements.
ThousandEyes Connect in New York City is November 9th. Registration is open.
Can't make it to New York? Maybe we'll be at an event in your area.
On to the big news! We are proud to release our latest new feature: Device Layer. We're digging deeper, down into the protocol stack to layer 2, to get you information and monitoring data from your network's devices. Check out the ThousandEyes blog post Introducing Device Layer: Diagnose Root Cause from App to Network Device from Product Manager Gopi Gopalakrishnan for more details on what Device Layer can do for you!
We're also very excited for ThousandEyes' appearance on the Packet Pushers podcast in early November. Tune in for a discussion of Device Layer and VoIP testing, or sign up for our Device Layer webinar.
Device Layer uses SNMP polling by ThousandEyes Enterprise Agents installed on your network to automatically discover network devices. Provide some basic configuration, and Device Layer will automatically find and monitor whatever SNMPv2c- or SNMPv3-capable device you want--routers, switches, firewalls, load balancers, wireless access points, and more! The data from Device Layer is provided to the Device Layer view, and is added to the Path Visualization view on any test with a Path Visualization that's run from an Enterprise Agent configured for Device Layer monitoring. Switch from the Path Visualization view to Device Layer view with a single click on a device.
Existing customers will have immediate access to Device Layer, with access from five monitored devices. Contact your ThousandEyes Account Manager for additional capacity.
Documentation for configuring Device Layer and for interacting with the Device Layer data can be found in our Knowledge Base.
More news of views... In order to accommodate future enhancements and maintain accurate nomenclature, the End-to-End Metrics view has been renamed to the Overview. Same great metrics; new view name. API endpoints are not affected by this change.
We've added a second IPv4 and IPv6 Cloud in Tokyo, Japan. This second Tokyo Cloud Agent, "Tokyo 2", uses NTT as its primary internet service provider.
Fixed an issue with Transaction tests causing a "Page load timed out (interrupted)" error message.
Transaction test errors now support UTF-8 characters.
We’re now forcing timeline alignment on full-width widgets for Reports & Dashboards.
Added IPv6 IP address to the tooltip of a Dashboard Enterprise Agent widget.
What's your favorite layer of the OSI model? Drop us a note and let us know the answer, or tell us whatever else is on your mind. Send us an email.
