←back to thread

How Netflix Accurately Attributes eBPF Flow Logs

(netflixtechblog.com)
160 points simplesort | 1 comments | 08 Apr 25 18:21 UTC | HN request time: 0.294s | source
Show context
thewisenerd ◴[08 Apr 25 20:28 UTC] No.43626119[source]▶
so they didn't want to pay for AWS CloudWatch [1]; decided to roll their in-house network flow log collection; and had to re-implement attribution?

i wonder how many hundreds of thousands of dollars network flow logs cost them; obviously at some point it is going to be cheaper to re-implement monitoring in-house.

[1]: https://youtu.be/8C9xNVYbCVk?feature=shared&t=1685

replies(2): >>43626400 #>>43626840 #
1. DadBase ◴[08 Apr 25 21:52 UTC] No.43626840[source]▶
I recall a time when we managed network flows by manually parsing /proc/net/tcp and correlating PIDs with netstat outputs. eBPF? Sounds like a fancy way to avoid good old-fashioned elbow grease.