The Kentik product team continues to crank out new features. Earlier this month we posted an announcement focusing on Synthetics. This announcement will focus on everything else.
My Kentik Portal (MKP) is a multi-tenant white-label network observability service that enables Kentik’s customers to market network analytics on top of their existing services. MKP is flexible and easy to use. MKP analytics data can be customized to serve customers’ unique requirements.
What’s New with MKP
My Kentik Portal has been ported to v4. In addition to everything available in v3, the new v4-based MKP comes with a new and streamlined landlord and tenant UI. Also, v3 was only available to Kentik Premier customers. With v4, we are now making MKP available to all customers (Classic, Pro, Premier).
A few noteworthy improvements brought with the v4 version include:
Introduction of Packages & Brandable Tenant Templates
While in practice the templates work the same, landlords now have the ability to brand them. The “Packages” tab will show the adoption of these packages across tenants.
An Overhauled View Assignment UX
Landlords can now see all the views assigned to a tenant at configuration time, whether assigned ad-hoc or as part of a template.
Options for Simpler and Safer Tenant Configuration
Tenant configuration now includes the ability to view the resulting filter as well as a direct option on all dashboards to “Preview as a Tenant.” This will append a clearly identifiable (named) filter group to the current dashboard filtering options and mimic what the target tenant will see.
Redesigned Tenant Portal UX
The redesigned tenant portal takes advantage of the screen’s real estate to display all of the analytics and alerting information at a glance. The improvements also allow for Guided Dashboard parameters to be entered directly from the landing page.
For some more detail on the new iteration of My Kentik Portal see Greg’s Villain’s blog.
Kproxy is now a first-class citizen in the portal, which implies the following:
Note that existing Kproxy-based users will see their Kproxies show up in the UI without the site, name and IP metadata associated with them. These can freely be updated as suggested by the UI.
In lieu of using Kentik’s on-the-fly reverse DNS, customers can leverage Kproxy and have it query their own DNS and insert rDNS values into the Kflow data. Among other things, it allows resolution of private IPs reverse DNS, but the initial tradeoff was that it cost customers two of their own custom dimensions. Upon rollout of this feature, native Kentik dimensions will be used.
Site IP Classification provides a way to define what site traffic originates from or what site traffic terminates to. This is particularly useful for our enterprise network customers to be able to track which data centers, branch offices, infrastructure hosts, or even employees are utilizing the network.
The configuration of this mapping is in the Manage Sites page in the settings.
In the following dialog, provide a comma separated list of IP CIDRs of the appropriate networks that are located at a particular site. Doing this configuration will tag each of your traffic flows with the appropriate values in the following dimensions:
New Settings Details Sidebar
Usability and design are very important to us at Kentik. We constantly look for ways to improve the readability and utility of the information that is presented. More importantly, we respond to our customer feedback. We have updated the design of a few of our most-used setting pages to provide a cleaner and more organized presentation of the most important aspects of your network — interfaces and devices. Take a look and let us know what you think by submitting your input via the “Feedback” link at the top right of the Kentik window.
We are now supporting the capability of overriding an interface’s IP address. This override works in the same way the other interface overrides work. Here are some example scenarios:
Users are now able to statically classify interfaces from multiple areas in the product. This feature provides a good way for companies with loosely-enforced interface naming conventions to be able to correctly classify their traffic. This feature allows users to benefit from the full breadth of Network Explorer and all modules relying on Interface Classification.
Important: Interface Classification attributes (Network Boundary, Connectivity Type, Provider) defined statically per-interface will always supersede dynamic rules defined in the Interface Classification engine. As a result, the dynamic interface classification UI will also show when such static definitions are set.
The rules evaluation UI has also changed so that statically classified interfaces appear as such when they escape dynamic rules, as they always supersede them. An orange checkmark will indicate that an interface is statically classified, as displayed in the screenshot below:
From the Settings > Manage Interfaces Screen
Multiple interfaces can be selected and bulk-configured from the top-right Classify dropdown, and users can also access a more complete Interface Attributes config screen from the edit icon button at the end of each interface’s row.
The interface screen’s right-side filter section will assist the user in identifying unclassified interfaces, statically classified interfaces making the manual classification process easier.
Additionally, this panel will also assist users in identifying interfaces that have been statically classified, offering the selectors displayed in this screenshot, prefixed with the “Overridden” mention.
Lastly, users will also be able to reset an interface’s static configuration from the single interface configuration screen, as depicted below, by hitting the “Restore” link:
From Any Network Explorer > Interface Detail Screen
As shown in the screenshot below: