Comment on page
Release Notes: 2014-09-17
This week, our team has continued prepping for our next couple of releases, which will be packed with new features that we're certain you'll love. We've managed to sneak a few changes into this release, most due to popular demand by our users.
We've updated the Enterprise Agent Status widget and added the capability to toggle between the Traditional Path Visualization view, which shows the path visualization from the agent to our Agent Collector, and the World Map, showing geolocation data for your agent. To configure the Enterprise Agent Status widget, click the gears icon and change the view from Path Visualization to World Map view, or vice versa. The screenshots below show examples of the widget's options:
We've modified a couple of our out of the box default alert rules, to reduce alert noise. This was done based on data analyzed across our client base, with input from several customers.
- Default Network Alert Rule has been changed to require a minimum of 3 agents showing 25% loss to the destination.
- Default Page Load Alert Rule has been changed to require a page load failure from 3 agents on 2 consecutive rounds.
We've also added a new metric for DNS+ Domain Trace tests. When setting up a Mapping is not in rule, you can add the option to alert when a percentage of mappings is above or below a certain threshold. Click the Add % of Mappings option after configuring this rule, to add a percentage constraint.
This rule was introduced to allow users to monitor changes to GLB DNS scenarios. As an example, consider the record www.company.com is mapped to 126.96.36.199 in North America, 188.8.131.52 in Europe, and 184.108.40.206 in Asia/Pacific. In the past, monitoring for specific record changes could result in a significant number of false positives. This option will allow more specificity in alert management, in order to allow alerting on regional changes with minimal numbers of false positives.
We've published a number of changes to v4 of the ThousandEyes API, in order to harmonize the feature set available on test creation and edit, between the user interface and the API. Check out our Developer Reference site for more details on these changes.