Netdata Community

Network: iface status params

Originally posted on GitHub:

Feature Request:

Inspired by #10628.

For ifaces we need to know about:

/sys/class/net/${iface}/ :

  • mtu
  • speed
  • carrier
  • lower_${parent}
  • operstate

If interface return invalid argument, for example for ‘gre’ interfaces, netdata should ignore this, or we need some white-list for iftypes.

This can be implemented after netdata: net: interface state: prometheus: used old metrics format · Issue #10671 · netdata/netdata · GitHub

@vlvkobal i think we could consider to add

  • /sys/class/net/<iface>/mtu

Indicates the interface currently configured MTU value, in
bytes, and in decimal format. Specific values depends on the
lower-level interface protocol used. Ethernet devices will show
a ‘mtu’ attribute value of 1500 unless changed.

  • /sys/class/net/<iface>/carrier

Indicates the current physical link state of the interface.
Posssible values are:
0 physical link is down
1 physical link is up

cc @k0ste

1 Like

mtu and carrier added in Add carrier and mtu charts for network interfaces by vlvkobal · Pull Request #10866 · netdata/netdata · GitHub

1 Like

@ilyam8 big thanks!
Finally deploy this to production


redirecting thanks to @vlvkobal :grinning_face_with_smiling_eyes:

1 Like


We are super happy that it’s useful now! Out of curiosity, what is your use-case and how come and you use the grafana dashboard and not netdata?

I assume that netdata exports to a prometheus db, right?

Cause Netdata is collector + exporter + what is going now on host (web), prometheus is functions, labels, storage and alerting, Grafana is visualaizer for all clusters/hosts/projects/business in one place (work with may data sources)