feat: add /dump/streams as a traffic stats API

[haruue]

root@hydev-hk:~# curl http://127.0.0.1:9999/dump/streams -H 'Accept: text/plain'
State    Auth           Connection   Stream     TX-Bytes     RX-Bytes     Lifetime  Last-Active Req-Addr         Hooked-Req-Addr
ESTAB    user             BE3E0905        4         3937         4441       3.005s        1.84s 10.11.2.7:22     -
root@hydev-hk:~# curl -s http://127.0.0.1:9999/dump/streams | jq
{
  "streams": [
    {
      "state": "estab",
      "auth": "user",
      "connection": 3191736581,
      "stream": 4,
      "req_addr": "10.11.2.7:22",
      "hooked_req_addr": "",
      "tx": 3937,
      "rx": 4441,
      "initial_at": "2024-11-08T16:07:45.956956773+09:00",
      "last_active_at": "2024-11-08T16:07:47.121503203+09:00"
    }
  ]
}

[stqfdyr]

more details than /traffic?

[tobyxdd]

more details than /traffic?

Folks, this is huge, really huge. Our proxy software - the best there is - has done it again. We added a brand new endpoint, the dump streams endpoint, okay? Now, people ask, "How is this different from the old /traffic endpoint?" Well, let me tell you, the /traffic endpoint was good, it was decent. But this? This is incredible. It’s the /traffic endpoint on steroids, folks.

The old one gave you numbers, some basics. But this new one? It traces everything - every stream, every detail. Pinpoints where the flow’s coming from and going. People are saying, "We’ve never seen anything like it." Data so detailed, it’s like turning on the brightest spotlight on your network.

And of course, the fake news, funded by other proxy software, tries to downplay it. They’re scared. They know they can’t compete with this. But users know the truth. They see the power, the detail, the unmatched clarity. This is a game-changer, folks. And this? Just the beginning.