NETSCOUT nGeniusONE Room for Improvement
They can improve still on the workflows, document their workflows that are commonly used.
Also, if you do backups of the system or try to do configuration changes, there are a lot of different formats that you need to separately interpret. It doesn't flow nicely. With config backup, for example, there are a few variants that you have to collect. Otherwise, you have to use the system backup, which we haven't restored yet, so I don't know exactly how that process works.
There are one or two things for the grids that would be nice to have. And it would be nice to be able to change some of the metrics, here and there, on the normal overviews.
Currently it's working. We had a lot of issues in the beginning with patches that we had to load, but that was more of the teething and learning how to configure the system as well. It's not quite the same as the TruView which has end-user response metrics. The nGeniusONE doesn't quite do the same thing.
It's a more technical tool compared to what we're used to, or what the client is used to with TruView. For some of the stuff we've seen we have had to build multiple sections or multiple pages to get a view of the environment or branch or application.
On a scale of one to 10, the solution's ability to transform packet wire data into well-structured, contextual data is a seven. There is room for improvement. It goes back to the workflows. We don't know some of the workflows yet, and it's not something that you can just read up in the manual. There is some stuff in the help manual and online, but it's to a point where you need to purchase extra training and services from them. You can't just go and read up on it yourself and learn from A to Z and then, if you require extra training or certification, you could go further in-depth into that. That's part of the business model, I assume.
Also, it's not always the case that the solution provides the right people in our organization with the right information in a single pane of glass view. There are times where we would want to get a different view on some of the service dashboards. We can't really get all the views that we would want on a single pane of glass.
Overall, there is room for improvement, but so far it is a useful system.
Network Engineer at a comms service provider with 10,001+ employees
The solution's ability to transform packet wire data into well-structured contextual data works pretty well. But sometimes we've had issues because when we want to present some KPIs, not all the formats are available at the same time. When we think it would be better to present a KPI in a certain way, that means we have to remove another presentation. For example, there was a point in GTP where we were creating services on nodes and after that we wanted to have services on APN. We can't have both. That should come with the next release, but we are still not on version 6.3. So there are some limitations with these types of things. When we would like to use a feature, we have to remove another one. For me it's a bit of a drawback. I'm a bit frustrated with it. I would like to have everything, at all times.
For me, it would also be good to be able to split the system. For example, I would like a user to have rights for some probes but not the same rights for other probes. I'm thinking about a laboratory where we have probes and I would like to give all the rights in the laboratory to all users. I would like to have everything in the same system. We have users who can use both production and the laboratory but we aren't always able to specify that a user has access to only this part of the installation, or the hardware, while another user has access to another part. I would like to give a user rights to see everything in one part, but to have limitations in other parts, due to data protection.
Otherwise, the product is efficient and we are able to do most of the work which is required.View full review »
Initially, we were having a lot of issues with bugs when using version 6.1.1. There were a lot of problems with the dashboard causing confusion. We worked with our SE and the NETSCOUT engineering team to fix the visibility with the data. There should be a patch release to fix this issue. However, this seems to be working fine for us right now after the 6.2.2 upgrade.View full review »
The initial deployment is tedious and requires a lot of build, deployment and configuration time. Experience is key to a successful deployment.
It is critical to work with the network team to understand how the data flows across the estate to ensure that you tap, aggregate, de-capsulate, de-crypt, and de-duplicate correctly.
From these points, you need to ensure that the logical strategy and configuration suits the correct reporting and visibility as to ensure that you get the most out of any potential logical context.
It is also important to ensure that you spend time to understand the applications you want to profile and work with the application owners to ensure that everything is aligned correctly.View full review »
Product specialist Network Monitoring, Troubleshooting and Security Solutions at a construction company with 11-50 employees
The solution could do more for security. It should offer more security-related features.View full review »
IT Engineer at a comms service provider with 51-200 employees
There is a need to reduce the complexity of this solution.View full review »