‹ BackHN Continuity

Thread

Nobody Is Listening on Port 8125

22 points · 15 comments · zasc

  1. theamk · · focus · HN ↗
    > 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.

    1. tucnak · · focus · HN ↗
      Maybe they wanted to play a bit with eBPF... The only reasonable conclusion. Wait till they go beyond localhost and discover XDP!
      1. r3tr0 · · focus · HN ↗
        haha we got xdp, tcx, BPF_MAP_TYPE_ARENA you name it ;)

        check the docs.

        <a href="https:&#x2F;&#x2F;yeet.cx&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;yeet.cx&#x2F;docs

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.