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
{{ message }}
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.
Similar to what spirent does it would be great if ostinato could be able to detect the interface speed and provide a speed gauge in Mbps were at a glance would be possible to see interface speeds.
a user could select if he wants to see only TX or RX or both.
Furthermore, Bps in today's network are irrelevant, we really should be looking at Mbps
The text was updated successfully, but these errors were encountered:
I think this a slight addition but if #246 is handled properly it could cover this use case.
The idea here is to have a view of how much traffic I am sanding at a glance. Like the gauge in the car, I'm not looking at historical data which #246 is asking for but rather at a meaningful snapshot of the current speeds.
Notice the word meaningful, because reading just a number "7,000,000,000" not only isn't quick to convert in Mbps or Gbps but also doest tell me if my interface has been saturated or not.
Maybe the gauge could scale Bps, Kbps, Mbps, Gbps based on traffic (i.e. If I send 10Gig of traffic of course I'm not interested in a few Kbps, but if I send only few packets, then yes bps and Kbps would be more meaningful)
pstavirs
changed the title
enhancement request - calculate physical interface port speed and visualize utilization gauge
Calculate physical interface port speed and visualize utilization gauge
Oct 22, 2020
Similar to what spirent does it would be great if ostinato could be able to detect the interface speed and provide a speed gauge in Mbps were at a glance would be possible to see interface speeds.
a user could select if he wants to see only TX or RX or both.
Furthermore, Bps in today's network are irrelevant, we really should be looking at Mbps
The text was updated successfully, but these errors were encountered: