-
Notifications
You must be signed in to change notification settings - Fork 15
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
Network Viewer program (bandwidth) #151
Conversation
, this is the basis of network viewer
This commit brings a map for a necessary function to work with sockets
This commit brings the global charts to the collector
Brings missing comments for the collector
/** | ||
* https://elixir.bootlin.com/linux/v5.6.14/source/net/ipv4/udp.c#L965 | ||
*/ | ||
#if NETDATASEL < 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we support both modes with kprobes? What's the industry standard for this type of monitoring? Maybe we can copy what most people are doing if it doesn't make much difference. In any case I don't see why we need to have 2 separate binaries for every collector, when we could just have one binary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The standard is not monitor errors, but I am bringing both to demonstrate users number of errors for these probes. This will also be used in the future with the developer log.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Part of netdata/netdata#8730 .
eBPF program to store socket information , this is the basis of network viewer, but the focus of this PR is to store information related to the bandwidth.