Skip to content

Network Monitoring on the Server #2301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ProxyBlocks opened this issue May 18, 2025 · 2 comments
Open

Network Monitoring on the Server #2301

ProxyBlocks opened this issue May 18, 2025 · 2 comments
Assignees
Milestone

Comments

@ProxyBlocks
Copy link

Is your feature request related to a problem? Please describe.
Right now there’s no way to see network usage over time. Would be super helpful to track traffic spikes or weird behavior like we already can with CPU and RAM.

Describe the solution you'd like
Add a traffic history graph – in/out bandwidth per Server. Like CPU / RAM 24h, 7d, 30d views.

Describe alternatives you've considered
Tianji has this, but only for live traffic, no historical view – so it’s not helpful for spotting past spikes or analyzing trends.

Additional context
Thanks for this project, it’s very helpful and lightweight
I like it :)

@gorkem-bwl
Copy link
Contributor

So Capture agent can get those values for us,meaning we can implement this in the next release. Thanks for opening this feature request.

image

@gorkem-bwl
Copy link
Contributor

Capture agent can send network details under /metrics/net(related PR: bluewave-labs/capture#67)

- BytesSent: Total bytes sent from the server.
- BytesRecv: Total bytes received.
- PacketsSent: Number of packets sent.
- PacketsRecv: Number of packets received.
- ErrIn: Incoming packets with errors.
- ErrOut: Outgoing packets with errors.
- DropIn: Incoming packets that were dropped.
- DropOut: Outgoing packets that were dropped.
- FIFOIn: Incoming packets dropped due to full buffer.
- FIFOOut: Outgoing packets dropped due to full buffer.

Attached is a mockup screenshot as well.

Image

@gorkem-bwl gorkem-bwl modified the milestones: 3.0, 2.2 May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants