Bug report summary
When a Netdata slave is rebooted, the IP bandwidth counter displays correctly on the slave's dashboard. However, when the slave is viewed from the master's dashboard, there's a huge spike (3.8 Gbps) just after the reboot. This is on a system with a gigabit interface. There are other systems where a reboot causes an even higher spike like 2 million terabits/s.
Master

Slave

OS / Environment
Debian Stretch
Netdata version (ouput of netdata -V)
netdata 1.11.1+dfsg-2
Component name
proc_net plugin
Steps To Reproduce
Set up netdata in a master-slave configuration and reboot the slave. Watch the dashboard provided by the master and see the bandwidth spike up after the reboot has completed.
Expected behavior
Netdata should handle the interface reset correctly and not display unrealistic values.
Bug report summary
When a Netdata slave is rebooted, the IP bandwidth counter displays correctly on the slave's dashboard. However, when the slave is viewed from the master's dashboard, there's a huge spike (3.8 Gbps) just after the reboot. This is on a system with a gigabit interface. There are other systems where a reboot causes an even higher spike like 2 million terabits/s.
Master


Slave
OS / Environment
Debian Stretch
Netdata version (ouput of
netdata -V)netdata 1.11.1+dfsg-2
Component name
proc_net plugin
Steps To Reproduce
Set up netdata in a master-slave configuration and reboot the slave. Watch the dashboard provided by the master and see the bandwidth spike up after the reboot has completed.
Expected behavior
Netdata should handle the interface reset correctly and not display unrealistic values.