Volumes & Sessions
The following two examples have been extracted from the same netflow information. The first picture shows the consumed bandwidth per protocol. In the second, the number of flows per protocol is displayed.
The result is typical for an office location. Bandwidth consumption is going up and down during a regular work day.
The evaluation of sessions (flows) however does not show periodic change. The protocols generating the most traffic are different from the protocols originating a high number of sessions:
- a single protocol group (TCP-Other) creates most sessions
- HTTP is the number one consumer of bandwidth (15,28%), but only responsible for 1,71% of flows
- ICMP is responsible for 4,25% of all flows, but only consuming 0,39% of the total bandwidth
IsarFlow's Drill Down functionality provides information to identify the session-intensive traffic by listing the top talkers and the related communication counterparts.
