<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello collectd community.<div><br></div><div>I'm wondering if it's possible to monitor network interface traffic on a per-IP address basis. In other words, can network traffic data be split out into Rx and Tx data for each remote IP address for each interface of the host server?</div><div><br></div><div>I've tried using the "--enable-getifaddrs" switch when making collectd, but it doesn't seem to change the output returned by the daemon. It's entirely possible however that I've overlooked something with using this switch.</div><div><br></div><div>One solution I'm considering is to create a custom plugin for this purpose. Development of this plugin would essentially involve modifying the "protocols" plugin to read from /proc/net/tcp (rather than the file /proc/net/netstat that is currently used by protocols). Before leaping to this solution though, I thought it would be prudent to check with the community to ensure that I'm not re-inventiing the wheel.</div><div><br></div><div>Any help or insights you can provide would be appreciated. </div><div><br></div><div>BTW, I'm working on a WebSocket-based interface for collectd called "collectdViewer". More info on this system can be found at: <a href="http://collectdviewer.com">http://collectdviewer.com</a></div><div><br></div><div>Regards,</div><div><br></div><div><div>
<div>John Bergmans</div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; ">Principal Engineer / Owner</span></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; "></span><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; ">Bergmans Mechatronics LLC</span></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; "></span><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; ">@jbergmans</span></div></div></div></body></html>