<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div dir="ltr">On 16. Apr 2019, at 00:21, Deepak Jain <<a href="mailto:deepak@ai.net">deepak@ai.net</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">I'm only aware of Sflow being IP/protocol/etc aware.</div></blockquote><br><div>Actually the sflow standard is flexible, and there are many fields widely available, including input interface and output interface, vlan/vxlan/mpls headers, etc. The sending device just needs to support the fields.</div><div><br></div><div>To give you an idea of some of the fields you can query from a TS server for example, here’s a description of one of the tables in the database: <a href="https://inmon.com/sentinel_help/8.0/help/en/report/api_view_traffic.shtml">https://inmon.com/sentinel_help/8.0/help/en/report/api_view_traffic.shtml</a></div><div><br></div><div>Browse <a href="http://sflow.org">sflow.org</a> for more fun info, including ideas for running sflow agents on your hypervisors (for eg correlating CPU and RAM usage per VM) etc :-)</div><div><br></div><div>Nick</div></body></html>