Please share with the community what you think needs improvement with NETSCOUT InfiniStreamNG.
What are its weaknesses? What would you like to see changed in a future version?
Regarding additional features, there is a competitor's product that has a feature that I wish NETSCOUT could employ. A company called Riverbed bought another company called OPNET, and OPNET had a technology that was fantastic in what it did and how it did it. One of the components of that OPNET product was called ACE, and if NETSCOUT could do something like that, it would be fantastic. That would give us the opportunity to look at what's called a Tier Pair Circle and see, in a more graphical way, what hosts are communicating with other hosts. That would be nice. In terms of room for improvement, the NetFlow Collectors could handle more flows per minute. The only other thing would be the packet flow switch being overrun, but that might be because we bought the wrong model packet flow switch. Instead of a 6000-series, we bought a 5000-series, so that very well could have been us. We didn't know exactly how much traffic was on the network until we put the tools in.
There is a timeout feature that we have been asking for awhile. The overall cost of the solution needs improvement.
I would like it to be more scalable with less spend.
The monitoring and reporting tool needs improvement. Users want more information, such as the level of detail when doing a packet analysis. They want more detail to be able to isolate down to a specific point.
It's not able to communicate with our probes.
The technology goes end-of-life on us every year, which is why I am looking forward to vSTREAM. I don't like when devices go end-of-life on us so quickly. If we can get more of an advanced notice of when an end-of-life is brought up, because our certification process within the organization takes a while. It takes us six months to certify a new one, or longer.
The training classes are great, but they go too fast. You can only get so much out of them. If you have experience with the tool, you can get a little out of the classes. However, if you have no experience, then the classes might be tough. They need to improve the training of the tool.
Being able to manage the packet flow switches in nGeniusONE would be great. We still need to get our engineering team more involved in the tool to help them understand how to use it a bit better.
I would like to see an improved level of stitching between IPs.
The single pane of glass feed still needs work. I do feel for what we have that it's fine. I would like them to simplify the interface when you go into nGeniousONE. When you look at your interfaces, they should combine them all, and instead of looking at an interface, have you look at events. Combine everything into one view.
We don't use the single pane of glass view. It's something that we are looking into since we do own it. We just don't use it at this time.