Nobody Is Listening on Port 8125(yeet.cx) |
Nobody Is Listening on Port 8125(yeet.cx) |
Naively the thing this is replacing sounds like a much better solution than the replacement is.
Though weirdly there's a part in the middle " 8125 is contentionally what statsd used" which should obviously have used "conventionally", so who knows which parts were written and which prompted for.
I'm reaching a point now where I'd really just rather see the prompts than these kinds of posts.
What in the slop is this?
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.
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.
we embed V8 directly and just point it at bpf
it has some really nice properties for dynamically instrumenting the OS.
and provides lightweight isolation for agents to control probes and do deep packet analysis.