I use this solution as a matrix for the traffic feed, for collecting the traffic from one server to another or from one link to another, and to write rules for firewalls. I mostly use it to filter traffic. I don’t use it to properly filter, but to have a better idea of what kind of traffic is entering my network.

The network technicians, network engineers, and security team need visibility. I can give them the information they need so that they can easily do their job.

Currently, two to five people use this for deployment and maintenance. Some people can work on the disc paths or storage. Others can take care of the applications or provide information regarding the application we want to feature or access. The system people can provide us the server they want to track or monitor, so that we can get all the traffic going in and out of those servers or applications. We can also involve the application, network, and storage teams.

If we have more infrastructure or equipment to monitor, we might increase our usage. We might add more units to provide better flexibility to get the traffic, etc. Right now, however, our current system is sufficient.

It's network monitoring performance and diagnosis. 

It has performed very well. It's very helpful when you want visibility into your network; not only visibility, but also the application performance and the packet captures and more. So it's very helpful.

We use this solution to generate metrics and get information about network traffic. It monitors both North-South and Easy-West traffic. This helps us to troubleshoot problems. For example, if a user is calling us and has some issue with the network connection, we can connect to the GigaStor and check the exact time to help find the problem.

We have an on-premises deployment.