kentik Product Updates logo
Back to Homepage Subscribe to Updates

Product Updates

Latest features, improvements, and product updates on Kentik's Network Observability platform.

Labels

  • All Posts
  • Improvement
  • Hybrid Cloud
  • Core
  • Service Provider
  • UI/UX
  • Synthetics
  • Insights & Alerting
  • DDoS
  • New feature
  • BGP Monitoring
  • MyKentik Portal
  • Agents & Binaries
  • Kentik Map
  • API
  • BETA
  • Flow
  • SNMP
  • NMS
  • AI

Jump to Month

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • July 2021
  • June 2021
  • May 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • October 2020
  • September 2020
  • June 2020
  • February 2020
  • August 2019
  • June 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • September 2018
  • August 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • April 2016
ImprovementService ProviderUI/UXNew feature
3 years ago

OTT Service Tracking gets a facelift and is now Capacity awaar

A lot of exciting news on the OTT Service Tracking workflow front this June 2021: not only does the entire workflow get a significant facelift, but our users are now able to visualize the state of capacity under every single OTT delivered via their networks, and drill in on the performance and audience impact ! See for yourself.


A significant UI/UX refresh

While working on adding this new functionality to the OTT workflow, information density has significantly increased, making the existing workflow harder to read. We have taken this opportunity to streamline it and reorganize content in it to make it clearer for users.

These screenshots illustrate the newly streamlined UX of the OTT workflow. We are now showing OTT traffic ranking in each category, where we initially only showed links to the different OTTs.

The engine classification rate which used to be a pie chart has also been reworked into a horizontal gauge to give more room to the actual usable data.

We have also reworked the OTT Service Details pages, not only to include OTT capacity, but also to better segment information in it:

  • An overview screen has been added that now shows comparisons/rankings to similar OTT services and ranking within the provider it’s part of.
  • The connectivity tab holds the usual former traffic slice-and-dice for the selected OTT service.
  • A new “subscribers” tab has been added which both holds augmented subscribership data for this OTT, and also a performance section allowing the users to slice and dice Mbps/Subscriber based on site, provider, connectivity type or any combination of these. The latter was not previously available in the OTT workflow.

Capacity as a Net New Functionality for the OTT Workflow

This extension of the OTT Service Tracking workflow was designed to meet the following requirements:

  • Being able to scorecard OTT services based on the capacity available to deliver them to the subscribers
  • Being able to dive into the details and see each interface on the edge of the network participating to the delivery of these OTT services to the subscribers
  • In case of high interface utilization, being able to determine the performance impact to subscribers whenever possible as well as the amount of impacted users.

We are now by default scanning the capacity for the top 100 OTT services for each customer and presenting the results in the Capacity tab of the landing page for the OTT workflow. Each treemap displayed on this page is a representation of traffic delivered by each interface (all devices included) and its utilization status.

The OTT service details page now also includes a tab for Capacity, providing an in-depth look at all devices and interfaces. The treemap shows all interfaces, and the list underneath is the list of devices involved. Each device entry listed below the treemap displays the contribution of its interfaces to the current OTT service and can be expanded to get details.

When expanding any device from the list, the user will see the details for each interface on the device involved in the delivery of this OTT Service.

Any interface within a device can also be expanded to display metric details around performance and the number of impacted users, taking into account the thresholds set for capacity in the workflow configuration.



Avatar of authorGreg Villain