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
My desktop's NIC is named enp0s25. A virtualbox guest of it has enp0s3. Neither of them produce ifstat metrics like linux_net_packets, linux_net_errs, etc. The code seems to require that the second line of /proc/net/dev must match this RE:
It looks like my NICs are being rejected on two counts. First, their names are not in the whitelisted list of patterns. Second, their names are too long, so Linux doesn't put a leading space (the \s at the start of the pattern.) For example:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
My desktop's NIC is named enp0s25. A virtualbox guest of it has enp0s3. Neither of them produce ifstat metrics like linux_net_packets, linux_net_errs, etc. The code seems to require that the second line of /proc/net/dev must match this RE:
\s(eth\d+|em\d+_\d+/\d+|em\d+_\d+|em\d+|bond\d+|team\d+|p\d+p\d+_\d+/\d+|p\d+p\d+_\d+|p\d+p\d+):(.*)
It looks like my NICs are being rejected on two counts. First, their names are not in the whitelisted list of patterns. Second, their names are too long, so Linux doesn't put a leading space (the \s at the start of the pattern.) For example:
By comparison, here's one that does work:
The text was updated successfully, but these errors were encountered: