In last month’s product update we announced Gauges Visualization that supports Bracketing to change the background color depending on user-defined thresholds. We have taken this a step further and extended the Bracketing capability:

• Bracketing now supports up to two Group By Dimensions (for more information on Group By Dimensions see our KB article) where previously it was only available for Total (no Group By Dimensions selected).
• We have added multiple methods for the bracketing threshold computation:
  • Static: user sets the threshold for each color manually.
  • Percentages: the threshold for each color is set as a percentage of the sum of all lines in the returned data.
  • Percentiles: the threshold for each color is set as the Nth percentile of the sum of all lines in the returned data.
• The Bracketing pane in the Data Explorer side panel is more compact and easier to read.
• Bracketing support has been added to both the Table and Matrix view types.
• Amongst others, it will:
  • Indicate which returned time-series scores the max value.
  • The feature is now compatible with multi-metrics: the primary sorting one will be displayed as the big value, the others on the right side of the gauge.

All of these are displayed in the example below:

For more information on using Bracketing, head on over to our Bracketing Pane Setting article in the KB.

We have now added the ability to get a Total Overlay line in a Time Series Line Graph in the Data Explorer. In the Data Explorer:

• Change your view type in the upper right-hand corner (above the chart) to Time Series Line Graph.
• In the Query pane of the sidebar click on the Advanced Options button to expand the additional options.
• Enable the Total Overlay selector.
• Click Run Query at the top of the sidebar.

At Kentik, we strive to get all of our customers as close to 100% Interface Classification coverage (more on Interface Classification via our blog post or KB article) as possible, where we find they get the best accuracy from this feature. In keeping with this, we have added a new General Settings pane in the Configure Interface Classification screen (Admin » Interface Classification » Configure Interface Classification), which allows the user to simply discard specific interfaces from the rules computation instead of configuring a default matching rule. In this pane, you will find the following:

• Exclude interfaces with no description
• Exclude interfaces with no IP address
• Exclude host (nProbe/kProbe) interfaces

The first two settings can be evaluated as AND or OR operations by changing the selector between them. The final setting is always evaluated as an AND operation.

We have released a new version 0.8.6 of our host agent, kprobe. While not particularly noteworthy by itself, this new version adds a couple new features to the Kentik Detect solution:

• UI Set Sampling Rate: Up until now, you had to set the sampling rate with a CLI parameter. Now, if the sampling rate parameter is not set, kprobe will determine the sampling rate by communicating with the Kentik Data Engine to receive the value set in the portal. This allows a more standard deployment of the agent where varying sampling rates may be required across the environment.
  
  
  

• First Payload Exchange Latency (FPEX) metric: This new metric measures application response time. After the TCP session is set up, this measures the time between the first request packet and the first response packet. This is especially useful for applications that Kentik cannot decode (HTTP and DNS are currently decoded). You will find this new metric in the Metrics drop-down menu in the Query pane of the Data Explorer sidebar (Data Explorer » Explorer View).

  
  It can also be used in Multi-Metric mode by click on Customize Metrics in the Query pane. You will find the FPEX metric at the very bottom right-hand corner of the Metrics dialog.

  This metric is also available in the Alert section of Kentik Detect. For more details on using the Alerting system, check out our KB article or Alerting Blog.

The information on the Device Stats view remains the same, although better organized. On the Device Details view we have added Interface Classification, CDN Attribution (shows a check if the device is configured to participate in CDN Attribution feeds), and Plan & Site to give the user more details about the device at a quick glance.

For more information about the redesigned Device List views, check out our KB article.

This will bring up the Register YubiKey dialog. Touch your YubiKey to fill the pane with a code and click on Finish Registration. You are now setup to start using your hardware key as an authentication method.

• Click on Admin » Devices » Add Device to load the Add Device dialog.
• Switch to the IP & SNMP tab.
• Set the SNMP V3 Auth selector to On
• Choose AES in the SNMP V3 Privacy Type drop-down menu

For more information on configuring SNMPv3 authentication, check out our Knowledge Base article.

In our November 2017 Product Update we mentioned that we have added the ability to start a manual mitigation as opposed to triggering one off an alert. We’ve now implemented this capability as an API and added it to the extensive list of REST APIs we’ve made available to programmatically manage Kentik Detect.

Our KB article contains more information and be sure to check out our API tester, which will help guide you on using this new method.