16 Apr
2019
16 Apr
'19
9:12 a.m.
On 16. Apr 2019, at 00:21, Deepak Jain <deepak@ai.net> wrote:
I'm only aware of Sflow being IP/protocol/etc aware.
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. 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: https://inmon.com/sentinel_help/8.0/help/en/report/api_view_traffic.shtml Browse sflow.org for more fun info, including ideas for running sflow agents on your hypervisors (for eg correlating CPU and RAM usage per VM) etc :-) Nick