+1 on that Randy. Excellent suggestions. I will also add:
- Manually selectable Link/Line colours (so I cam make things like Blue=Copper, Yellow=SM fibre, Orange=MM fibre, etc..) - Line point weights (i.e. 10g is thick, 1g is thin, 100m is 1 pixel.... Had a thread about this a while back to 'raise the floor' for calculating line weights.. where 100m is now the 'reference bandwidth') - Netflow - Ability to do queries based on the origin-AS attribute. ......Not to beat a dead horse, but this is what ISPs use Netflow primarily for. Not to necessarily look at their 'top 20 customers' out of the 200,000+ or 2Million+ they have, but to look at where the majority of their transit traffic is going to/from (By AS Number). Note that the Netflow-speaking router is *already* calculating and including in the origin-as information in the Netflow data it's sending *right now* to IMFlows). This is useful so we know who to setup bilateral peering relationships with to offset Global Transit costs. Just need to expose a way to 'get at that data' in the GUI. - CK. On 2012-03-21, at 3:58 AM, Randy Baker wrote: > 1: I would like to add a label/smart label to a link. I would like to > create my maps to look similar to the following example by including the link > speed, current throughput, thresholds, colored link and ants. > netstat.ayy.fi/weathermap/<http://netstat.ayy.fi/weathermap/> ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
