You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered:
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're definitely planning on adding direct metrics similar to the statsd ones from the DPDK version in the coming weeks as we look to get to feature parity on the XDP version. 👍 👍
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 theglb-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?
The text was updated successfully, but these errors were encountered: