Operations | Monitoring | ITSM | DevOps | Cloud

We’re running down the latest developments, releases, and features in the latest What’s New at Kentik. This episode features improvements in report processing, enhanced report features, and updated Synthetics alerting to transform data into actionable insights. Remember to like and subscribe for more Kentik product updates each month!

In AWS, even a tiny misconfiguration in security groups or routing tables can lead to significant traffic blockages. Watch this short demo highlighting how Kentik can diagnose these issues and use enriched flow data and contextual analysis to find the root cause of traffic blockages.

Are performance-impacting hybrid and multi-cloud issues affecting your business’ happiness? Introducing Kentik (Observabilium) Daily, a revolutionary new full-featured solution to your organization’s cloud network observability needs.

Phil Gervasi shows the importance of understanding traffic over AWS Transit Gateways for cloud cost management. He demonstrates how Kentik provides a visual layout of the entire AWS environment, including Transit Gateways, and allows users to dig into specific details and metrics. Phil also gives a quick look at Data Explorer, where users can observe Transit Gateway traffic over time, create and edit filters, and customize data visualization for sharing and exporting.

Host Leon Adato takes you through the latest updates and features from Kentik. This month, we dive into monitoring analytics for content distribution networks (CDNs), explore the new Use Case Finder in Kentik's knowledgebase, and learn how to include custom fields in Data Explorer. Plus, Leon shares some light-hearted insights on why August is the perfect time to celebrate with Kentik's... uhh... craft brews? Don't forget to like and subscribe to keep up-to-date on everything new at Kentik!

Phil Gervasi introduces a method for identifying idle resources in AWS using the Kentik platform. By selecting dimensions such as Logging Status, Observing VPC ID, and Observing Region, users can filter the data to determine if a resource is actually doing anything from a network perspective. “No Data” messages indicate resources with no network activity, and a more specific filter can be created based on this message to isolate idle resources. By adjusting the time frame and observing bits per second, users can determine how long resources have been idle.