Kentik

SEPTEMBER 11, 2018

Network elements that support traffic monitoring protocols such as NetFlow and sFlow extract critical details from packet flows, like source, destination, byte and packet counts, and other attributes. What is NetFlow? NetFlow records can be generated based on every packet (unsampled or 1:1 mode) or based on packet sampling.

Network 66

Network Load Balancer Big Data Analysis 66

Kentik

JULY 20, 2018

NetFlow is a protocol that was originally developed by Cisco to help network operators gain a better understanding of their network traffic conditions. Cisco started by providing NetFlow exporter functions in their various network products running Cisco’s IOS software.

Big Data 40

Big Data Analysis Network Storage 40

Kentik

AUGUST 28, 2019

Steaming telemetry uses a push-based mechanism with which data can be transmitted automatically and continuously from various remote sources (such as routers, switches, firewalls, etc.) to some centralized platform for storage and analysis. device sends data to collector) versus Dial-in (i.e.,

Network 16

Network Analytics Metrics Technical Review 16

Kentik

APRIL 6, 2021

In this blog, I’ll walk you through how you can configure your AWS environment to target precisely what you want to monitor — nothing more, nothing less. At a high level, our goal is to insert a flow log source into the data path between your VPCs and the internet. The “Gimme Everything” Approach to VPC Flow Logs.

AWS 98

AWS Network Cloud Internet 98

Kentik

APRIL 24, 2017

But first, based on that fundamental distinction, let’s classify common flow protocols accordingly: Stateful flow tracking : — NetFlow : Originally developed by Cisco in 1996. IPFIX : The IETF standards-based successor to NetFlow, sometimes referred to as NetFlow v10. . The most used versions are v5 and v9.

Internet 40

Internet SMB Network Analysis 40

Kentik

JANUARY 26, 2016

Our initial task was to enable fast spelunking of network traffic data, both present-time and historical, to help operators see and understand what’s happening on their infrastructure. By mapping the customer’s traffic merged with topology and BGP data, we’ve now done that in Kentik Detect. Launch peering analysis on the BGP dataset.

Analytics 40

Analytics Analysis Network Data 40

Kentik

OCTOBER 25, 2016

In the prevailing appliance-based model, an out-of-band appliance detects attacks based on NetFlow, sFlow, IPFIX, and BGP data. Segmented rather than network-wide views of traffic data. That encourages the segmentation of data into more predictable buckets. Big data to the rescue. Limits of the status quo.

Scalability 40

Scalability Architecture Big Data Analytics 40

Kentik

DECEMBER 2, 2015

One of Kentik’s big ideas about network visibility is that it should be possible to identify and alert on any network anomaly even without advance knowledge of the specific threats you’re guarding against. Kentik Detect is ideal in this regard because it’s able to ingest full resolution flow records (NetFlow v5/9, IPFIX, sFlow, etc.)

Windows 40

Windows Network .Net Groups 40

Kentik

DECEMBER 15, 2015

Source Geography Analysis in Data Explorer. Specifically, we’ll look at how, starting with a simple source-geography analysis, we can use Kentik Detect’s Data Explorer to discover interesting and potentially important DDoS and other attack vectors. Getting Beneath the Surface.

Analysis 40

Analysis Metrics Groups Network 40