We've been using the DPDK glb-director but had issues with driver support, so we're trialling using the XDP implementation instead and first impressions are excellent.
However, the DPDK version had dpdk-procinfo and statsd exporting from the glb-director process for understanding packets and bytes received and transmitted.
It seems that we can get some semblence of XDP network throughput statistics via ethtool -S $interface but it is again driver-specific and doesn't give XDP-only traffic metrics. The xdp project acknowledges that metrics for XDP are inconsistent at this time, and suggests that each XDP program does it's own accounting, one example of this is given here.
Is there already a source of traffic data for glb-director-xdp or would custom solution per the above example be necessary? Is metrics support planned or would it be considered?
We've been using the DPDK glb-director but had issues with driver support, so we're trialling using the XDP implementation instead and first impressions are excellent.
However, the DPDK version had
dpdk-procinfoand statsd exporting from theglb-directorprocess for understanding packets and bytes received and transmitted.It seems that we can get some semblence of XDP network throughput statistics via
ethtool -S $interfacebut it is again driver-specific and doesn't give XDP-only traffic metrics. The xdp project acknowledges that metrics for XDP are inconsistent at this time, and suggests that each XDP program does it's own accounting, one example of this is given here.Is there already a source of traffic data for glb-director-xdp or would custom solution per the above example be necessary? Is metrics support planned or would it be considered?