> We replaced the listener with an eBPF program that watches port 8125 at the traffic control layer of every interface, and a JavaScript decoder that turns the lines into Prometheus families.
this is insane! Why on earth would one to replace a short, simple, highly debugable program with this crazy combination. Why would you trade a simple socket(2) call which shows up in ss, netstat, strace etc.. with something that opaque? Especially given the bandwidth is minuscule and the destination is already localhost.
theamk · · focus · HN ↗
this is insane! Why on earth would one to replace a short, simple, highly debugable program with this crazy combination. Why would you trade a simple socket(2) call which shows up in ss, netstat, strace etc.. with something that opaque? Especially given the bandwidth is minuscule and the destination is already localhost.
cookiengineer · · focus · HN ↗
Your past experience limits your thinking, especially in agentic environments.
But I suppose their whole business model is built upon that, given that yeet is a bun/node/deno library with bpf support.
r3tr0 · · focus · HN ↗
we embed V8 directly and just point it at bpf
[deleted] · · focus · HN ↗
[deleted]