The sFlow mechanism is OVS is inherently ingress-only sampling, so per-port config would rarely make sense as it would result in only half the picture for a given VM or link. The sFlow philosophy is to keep the agent as simple as possible and generate a standard feed that can be used by more than one application. So if a particular application requires a special filter to be applied, then that should be done at the collector.
(It's not hard to receive an sFlow feed and forward a subset of it on. Deploying a "first-receiver" sFlow collector to provide this filtering-and-forwarding step has been done before. The filter may be on ports, CIDRs, MAC addresses, protocols... It wouldn't make sense to push all those features into the switch.) ------ Neil McKee InMon Corp. http://www.inmon.com ------ Neil McKee InMon Corp. http://www.inmon.com On Mon, Mar 25, 2019 at 1:39 AM 王志克 <wangzh...@jd.com> wrote: > > Hi, > > > > Per below OVS document, we can configure per bridge sflow. > > http://docs.openvswitch.org/en/latest/howto/sflow/ > > > > $ ovs-vsctl -- --id=@sflow create sflow agent=${AGENT_IP} \ > > target="\"${COLLECTOR_IP}:${COLLECTOR_PORT}\"" header=${HEADER_BYTES} \ > > sampling=${SAMPLING_N} polling=${POLLING_SECS} \ > > -- set bridge br0 sflow=@sflow > > > > My question is: > > Whether we can configure sflow per in_port or egress port? Basically we may > only have interest for certain traffic. > > > > Br, > > > > Zhike > > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss