Network Observability
summary
Erlang-based InFlow collector parses sFlow and IPFIX via binary pattern matching, runs gen_udp receivers that hand work to parser workers, and handles template state by broadcasting IPFIX templates over a PG group. Flows route to Island shards using P_hash2 sharding into per-key edge tables, are aggregated per minute with sample aggregator hibernation to save memory, and publish via Hackney to Kafka. System processes about 800k datagrams/sec (~5M flows/sec) and emits ~3M aggregated messages/sec.
AI-written summary · about
chapters (5)
- 0:0002:02 - Intro and Agenda
- 2:0307:15 - Intro to InFlow
- 7:1611:15 - Applications of Flow Data
- 11:1622:18 - InFlow Collector Architecture
- 22:1941:22 - InFlow Collector at Scale
related talks
26mNetwork Observability with IPFIX, Prometheus and Elastic Stack
49mRelational Observability for Cloud-Native Security and Data Science
16mNetwork Flow Data in the Cloud
35mNetwork Flow Monitoring in Kubernetes with Contiv/VPP CNI and Elastic Stack
39mManaging (..) networking flows using Erlang
23mNetwork Flow Aggregation: Pay for the Logs You Care About!
28mEasy logging refinement with FlowG
35mNetwork Flow Monitoring in Kubernetes with Contiv/VPP CNI and the Elastic Stack
