You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# ethtool -g internal0
Ring parameters for internal0:
Pre-set maximums:
RX: 4096
RX Mini: n/a
RX Jumbo: n/a
TX: 4096
TX push buff len: n/a
Current hardware settings:
RX: 4096
RX Mini: n/a
RX Jumbo: n/a
TX: 4096
RX Buf Len: n/a
CQE Size: n/a
TX Push: off
RX Push: off
TX push buff len: n/a
TCP data split: n/a
Importance
nice to have
Value proposition
Being able to monitor hardware queues and statistics can help find otherwise hard to find problems with the network. Especially advanced/high endnetwork cards have multiple offloading and other features that could be problematic if not monitored closely.
Proposed implementation
As far as I know it is only possible to monitor these hw statistics using ethtool, but there is probably an interface that could be used directly.
The text was updated successfully, but these errors were encountered:
Have there been any attempts to add this to netdata? Yes, for example #14674
The implementation of fields from the driver requires a special approach to normalize the metrics. That is, what you presented for Mellanox will not work for Intel. And it won't work for virtio, at least. To solve this the plugin need at least a parser, a good example of implementation that I can give is a project ethq where the parser determines from the driver name what it needs to look for (example)
Currently netdata don't have any part of ethtool interface, but if this interface will be available, there will be another parts that's may be covered:
What this implementation gives to netdata product - expansion of equipment on which netdata will be indispensable! 'White boxes' - the Ethernet Switches with linux as control-plane, for example Edge-Core will be added to servers and virtual machines
Problem
Hi, I think it would be valuable to be able to monitor the hardware statistics of network interfaces.
This would allow you to see things like queue overruns, checksum errors and other things happening before packets reach the Linux network stack.
I have had a case where the hw queue was too short and the nic dropped ethernet packets. Using ethtool i could see this and increase the queue length.
Description
These can be viewed using
ethtool -S eth0
.Importance
nice to have
Value proposition
Being able to monitor hardware queues and statistics can help find otherwise hard to find problems with the network. Especially advanced/high endnetwork cards have multiple offloading and other features that could be problematic if not monitored closely.
Proposed implementation
As far as I know it is only possible to monitor these hw statistics using ethtool, but there is probably an interface that could be used directly.
The text was updated successfully, but these errors were encountered: