The main goals of this article are to (1) provide you with examples of Traffic Patterns and their usage and (2) to give you an idea on how to create your own Traffic Patterns. In this article only basic Traffic Patterns, that can be created with only IP address ranges and de-duplication filters, will be explained. For advanced examples, see Advanced Traffic Patterns.
General workflow for creating new Traffic Pattern:
Below are two most common examples of Traffic Patterns.
All Traffic Pattern gives the answer to "How my network is communicating to the rest of the world?". Here your company's IP address range is treated as Internal network, whereas all other (both belonging to your company and not) as External network.
By default, NetVizura provides All Traffic Pattern with predefined IPv4 address ranges (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16). However, if your company uses different IP address range than predefined you need to change All Traffic Pattern. Since this is practically the traffic between your network and everything else you should select Custom type and update Internal IP addresses leaving External empty. In the end, you should use Exporter or Next Hop filtering to remove eventual duplicate flows, if needed.
If you are interested in monitoring Internet traffic, first you need to prepare a specific Traffic Pattern for this purpose. Since this is practically the traffic between your network and external world where External network is negation of Internal Network) you should select Normal type which will automatically populate part of the IP address ranges. Here your company's IP address range is treated as Internal, whereas all other networks as External. In the end, you should use Exporter or Next Hop filtering to remove eventual duplicate flows, if needed.
Note that subnet nodes in a Traffic Pattern are shown only if they are included in the Internal Network in the Traffic Pattern definition. |