[ixpmanager] [RELEASE] V5.5.0 - Member Port Utilisation Reporting

[Barry O'Donovan]

Hey Rob,


Rob Lister wrote on 23/03/2020 14:34:
> This is a much needed feature - thanks for implementing it at this
> time.

Cheers :-)

> A couple of thoughts come to our minds, if you update this in a
> future release:-
> 
> 1. Would be more useful to have the option to calculate it to 95th 
> percentile to avoid it flagging up temporary traffic spikes.

Separate to what Nick said on this, I'm uneasy about implementing 95th 
percentile here. If a port is exceeding a level of utilisation that 
triggers the IXP to start the discussion on upgrading then I don't see 
that it matters if it's at 95th or not. As IX's we're interested in 
ensuring packets aren't dropped and they will be dropped whether the 
cause is spikes or normal usage.

> 2. VLAN column seems redundant since at the top, it filters by VLAN 
> already.

We have >1 peering LAN so it has use for us and others like us. Not sure 
if I'm missing your point...

> 3. A way to filter out certain ports, for example Netflix and some
> other CDNs have the ability to max out a port without congestion
> since they have tight software controls on what gets delivered where.
> (customer flag or a field like the "Active Peering Matrix" to exclude
> some members.)

If such a CDN has a 100Gb port and is flatlining (albeit without 
dropping packets) then I still want to know because there's pent up 
traffic demand there.

That said, I do also see a use for what you're suggesting and I've had 
something similar in mind so I'll see what I can do here. Best thing to 
do here Ron - if you're interested in seeing this happen and track it - 
is to open a feature request on Github. We'll probably get there anyway 
but it may move it along :-)

  - Barry