NETSCOUT Network & Application Observability Reviews

My primary use case of this solution is the monitoring of network devices, security devices, servers, and so on.

There is a need to reduce the complexity of this solution.

The stability of this product is ok.

Technical support for this product has been ok, with no issues.

The initial setup was complex, and deployment took around six months.

I used consultants for deployment.

This product is suitable for high-level enterprises, but I would not recommend it for small-to-medium enterprises. I would rate this solution as five out of ten.

Most of the time, the use case is if, for example, the network is slow or an application is slow and you don't know why, and you need something to look for the root cause of the problem. With NETSCOUT, it's very easy to check where the problem is located. You can uncover if it is in the network or the application or the server.

It's easy to use and easy to pinpoint where the problems are if ever something is slow. 

Most of the time the customers are complaining that the system is slow and you need to know why something is slow. It will give you insight into the underlying issue, which is very helpful.

The installation process is straightforward. 

Technical support is very good.

The solution could do more for security. It should offer more security-related features. 

We have had NETSCOUT for a long time. In the past, it was part of Fluke Networks, and then Fluke Networks was bought by NETSCOUT. Then, we were working together with NETSCOUT,  acting as a reseller for NETSCOUT solutions. We have been working with them for more than 10 years and of course before that, with Fluke Networks.

Technical support has been good. They do not need to improve it. We've been satisfied with the level of service on offer. 

The initial setup is very straightforward. It's not overly complex or difficult. I found the process to be very simple. 

It's a hybrid solution. You can use both cloud and on-premises deployment models. 

We are not the users of this solution. Rather, we are the reseller. We are a local reseller for these kinds of products within Belgium. We also have a company in the Netherlands, it's for the Benelux region. We have customers in Benelux and we are acting as a reseller and we sell the solutions and the support which we do ourselves. For me personally, I'm located in Belgium. I handle the Belgium market and Luxembourg, however, I have colleagues in the Netherlands and they do the Netherlands market.

I'd rate the solution at an eight out of ten. I've been pretty pleased with its capabilities overall.

I would recommend the solution to other users and organizations.

This solution has been implemented at banks and retailers to focus on network-based application performance management.

Aligning the solution with a visibility layer (taps, aggregation taps, and packet brokers - Ixia and Cubro), NMs system (Sintrex) we were able to deliver information relating to various applications and their behaviour.

Creating an environment where you triage a problem quickly and provide valuable information allows for improved MTTR.

This allows for a cross-silo approach, enhanced visibility, which enhances IT to better service the business.

We have partnered with Netscout over many years with various solutions - TruView, nGeniusOne, Infinistream, XG, etc.

With the focus on customer-defined applications and triggers we have been able to provide important information to clients regarding their application performance.

It has played an integral part in providing valuable information in a critical arena.

The ability to use pre-defined applications and configure client-specific applications allows for a comprehensive solution that enables all teams within the IT organization.

The combination of triggers with the ability to generate alarms.

The ability of the dashboards is useful for discover, mapping and understanding of application behaviour.

The ability to define client-specific applications.

If required, you can view up to a millisecond of what the behavior of the application is.

The ability to give insight into assigning the problem, with relevant information, to the correct team.

Detailed reporting that can be built with various perspectives and metrics.

Various dashboards can be built to service various applications or security teams.

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.

We have been using this solution at multiple clients for many years.

In general, the stability is good, but we have had one or two incidents where specialized support was required.

The solution can scale in most directions, bandwidth, hardware, virtual taps, etc.

We have a good relationship with the vendor. They are always willing to help, but due to the complexity of the environment solving problems can take some time.

We have previously made use of nMetrics, Spyke and older versions of the Netscout product range and still make use of ExtraHop Reveal (x).

We do however try to fit the need of the customer to the best solution and the vendor they prefer.

Initial setup and configuration is complex and tedious and requires a methodical approach with experienced engineers.

For complex implementations, we rely on the vendor for more support.

The return on investment is directly linked to the deployment, configuration, and management of the solution.

If you make it a priority, you will experience good ROI.

It is important to spread the cost across the various IT silos as this solution works as an umbrella to provide information to all teams.

Try to target major aggregation points in your network to deliver the best potential data to the solution. You can from that point start to target specific areas to resolve specific issues or gain particular insight into certain areas.

Do not forget applications traverse North-South as well as East-West and in layers of those. Think about your typical WAN breakout, Layer 2 connections, Virtualized environments, and servers supported by back-to-back connections (eg. web server supported by DB server, with a direct connection).

Sintrex Flow Module, ExtraHop Reveal (x) - the reason we went with nGeniusOne was because the client has that they require a specific solutiion that NetScout answers, already deployed other Netscout solutions or that they had a specific function in mind (eg. InfiniStream tagging)

It is always important to understand the problems you are trying to solve, what insight you are trying to gain and that this is a solution for the business, not just a specific IT silo or team. 

It's deployed at a customer in the banking environment and it monitors the perimeter edge in the data center. It's used for visibility inside the environment as well. The traffic is only being sent via TAP data currently. We don't have any NetFlow data to the system, as yet. We have the NETSCOUT TruView system in and that performs for TAP data and NetFlow to monitor the branches.

For some of the applications we've managed to drill down and get more granular data, because it provides such small granularity — a microsecond or a millisecond of data — that you can actually get finer response-time detail out of it. That helps a lot.

It has improved some of the visibility of some of the unified communications with the ability to drill down into finer time increments in the packet data. We are able to search through those and get those Wireshark-types of views, with some extra flexibility and visibility on packet data or wire data.

The quick drill-down views are similar to Wireshark views. Those are quite nice, with the views on how you interpret some of the data. The granularity of how far you can drill down into milliseconds or microseconds is a very nice feature. It actually stores quite a lot of data in its database. It enables drilling down for reporting.

The solution transforms packet wire data into real-time data that is ready to act on. We've set some of the alerts to alert on it. We can look at that packet data, or we'll use scenario-based alerts, to then further drill down and see what the system has picked up as an anomaly or a scenario that's being analyzed by the system. We can investigate it further and see how we can resolve the issue or alert on it for the client.

We received some documentation to integrate it with ServiceNow. We're busy looking at that for the near future to integrate into that or another vendor's ticket system, and then alert on things in real-time, so there's less delay from our interpreting of data first. And then we can act on it.

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.

We deployed NETSCOUT nGeniusONE last year around April, so it's just over a year now.

Currently we're running quite stable. There were a few hiccups in the beginning with stuff not working. But currently we're running more or less stable. We are running on version 6.2.2. There are a few useful things in 6.3, but we were advised not to go that route yet because it's not 100 percent stable. Our sales engineer said to hold on, just to see how some of their other clients experience it and see how many issues are still being noted in the system before we move over to that newer version.

We'll probably increase visibility in future because it needs to replace TruView. Currently we are only using packet TAP data. Later on, as NetFlow and those things evolve, we will need to move over to NetFlow collectors on the system as well. Currently we're using them on TruView.

And we need to expand to some of the newer data centers that the client has moved into, as well as the cloud section. We need to expand into those as soon as the client has a bit more budget and they are happy that the system is working and the views and the consolidated views are giving them what they want. Then they'll expand more on the system.

The key thing for us is to get the VAR service up and running, which should be starting from today. They've sorted out their remote access. That took us a few months just to get into the banking environment with all the nondisclosures and security checks. We are quite happy to get that started and to see how they can assist us on the system. We want to do a sanity check on the system to see what we've missed.

We have an account with them and each engineer has an account where they can log TAC cases, and our sales engineer sees some of the stuff that we seldom hear and assists where he can. Otherwise, we work with the guys overseas. It depends which section of the system it is for unified communication. Cases have been escalated, eventually, to assist configuring some of the things.

We've had a few issues with one of the InfiniStream storage units, and that took a long time to resolve. The guys are still learning some of the things on the system themselves, but that eventually got resolved. But that may also depend on the support model we took.

Once you get to the higher-tier support guys, your issue normally gets resolved quite quickly.

We've been using TruView. We've known for a while that we would need to switch because it was an old Fluke Networks product which was bought by or moved to NETSCOUT. We knew at some point in time it was going end-of-life. We need to keep it up and running for as long as possible, at least another two or three years, until the end of the contract, and see how long it lasts after that. Slowly but surely we'll migrate to nGeniusONE as we expand visibility.

The setup was a bit complex, documentation-wise. There is a long list of documentation just to deploy the system, with a lot of variations. There's tons of documentation. Their portals reflect all the documentation and you need to go through various sections of the documentation to find what you're actually looking for.

We managed to get it in in a weekend. It was a relatively short time just to get the equipment in. The InfiniStream we took uses attached storage. It has an IPMI which wasn't mentioned in the original deployment documents. I managed to eventually find out what the base system is, a Supermicro server base. I then managed to get documentation around how to configure it and what the default IP address is for those. I had to configure that, because there are certain things that you can't do if you don't have that to update the firmware of your storage array — shut it down, restart it, those types of things. That wasn't on the original one-page install glossy.

It's a lot different than what we're used to in terms of the various sections that you need to configure. The workflow for some of the stuff could use some improvement. It sometimes feels like the system is silo-based or sectional-based, and that it was then all put in one system. There isn't just one place you can configure your application site or a quick-start "how-to." If you want to configure an application and then get it on your dashboard or your service views, it would be nice if it gave you an auto wizard which would say, "You want to configure an application? Okay, next." You would fill in what is required, click "next" to get you to the next step and keep on following the same workflow so that you can't really deviate. If you know which sections you want to configure, maybe then you would configure it manually, but a wizard-based workflow that's set out to be followed would be good.

As we learn stuff we've transferred the knowledge to our client and they have learned themselves as well, playing with the system. As they run into a workflow issue, then we try to assist or we contact our sales engineer to ask if there is a better workflow for some of this, and how to get to the pane that we would want to be on more quickly. For some of it, there was a quicker way, and for some of them the system is built in such a way that there is not a quicker way to get to some of the views.

It requires quite a lot of staff to set up and manage the tool; there's quite a learning curve. What we normally like to do is load it offsite, deploy the system, prepare it properly, get the base configuration on, and load at least some of the applications, but we didn't have the luxury of that kind of time. It took us a bit of time compared to what we've been used to on the TruView. We tried to configure the applications, but it's not quite the same. In workflows we've missed things here and there, things like going to a different view to associate applications to a site or an interface. We missed that at times. That's where the automated workflow wizard would help a lot, to make it easier for anyone to use the system, to climb in and start configuring it.

We're still busy streamlining and working on our alerting, to get those properly set up. NETSCOUT, from their side, is PoC-ing the VAR service to assist us for three or six months in streamlining the system, see where we're running short, and also to do system checks and see what else they're going to have to improve on the system.

We're not really a proactive system yet because we're still trying to define some of the things. The system is not at a scale where it can monitor each and every thing. There are a lot of things in the environment that we learn and get to know of on a daily basis, as they deploy new things. There are also things that we've not heard of because some of the environments are still silo-based.

I don't know what the client is looking at, because they can acquire from other vendors.  Because we're part of the networks team, we're more focused on the actual network component.

It's not an easy system, it's a very technical system. There are some views that you could get for a management or objective overview. Even our client mentioned that it's more a technical tool. That comes back to the workflows and the drill-down and the amount of time you spend to drill down into a scenario. That sometimes makes it too long in a real-time troubleshooting scenario or focus session. That makes it a bit difficult. If there's an outage in the environment they might start looking at you because they're waiting for you to provide information. I assume that would improve a bit when VAR service comes on board to show us what we're missing and how we can set up scenarios or extra alerting on the system to improve drill-down and the time to respond to or the time to resolve issues.

It does auto-discover some of the stuff. I don't think we've really used everything that's available. We've used some of the auto-discovery for URLs or web-related links, as it picks them up. We've used some of those and then we further define it. I'm not sure if there's another way or extra things that can auto-discover. Normally we'll get an application and environment from the client, and then we'll define it from there, or we'll use TruView to look at the NetFlow data to see what ports, for example, are being used. Then we will interact with the client to further see what is there. Or we can use nGenius' packet data and pull down what ports are being used from there. Then we can go back to the client and say, "You said port 123," for example, "is being used. We see 123 and another port. Is this other port also part of your application, or what function does it have in your applications?"

As for whether nGeniusONE helps us to get to root cause quickly, it's "yes" and "no." It fits in more with some of the workflows that we're still learning or we may not have the correct workflow. We've learned quite a lot over the last year or so but there is some room to improve, or it might be something that we don't know about; how to navigate a bit faster and better. One thing the client did say, if you compare it to TruView, is that with TruView you get to most of your issues in three clicks. In nGenius you need a few more clicks just to get to where you want to be. And sometimes you need to take a different route through the system to navigate to a different view.

When it comes to seeing a measurable decrease in mean time to repair, or mean time to know, there might be some workflows we're missing, that we don't know. We've used the system now for just over a year, and we're constantly learning new ways to configure the system and new workflows and how to improve our troubleshooting time. But compared to our older TruView system, it takes a bit longer to navigate to certain sections of the system or down to where we want to be, to the packet data, or to drill down into some of the applications.

We use nGeniusONE for Microsoft Teams. There is a case that we want the VAR service to take on for us to tie up some of the communications from external to internal Teams calls as they pass through the firewall. We're going to look at that to see what the VAR can assist us with. The client needs to expand on some of its TAP-ing visibility as well when, in the near future, they change their design.

As far as I know the solution has not enabled us to consolidate tools, because our client uses various systems. An example is Dynatrace as an internal banking application that they use for Layer 7 and agent-based monitoring on some of the servers and applications. And we still use TruView. Then they're constantly expanding to see where they can add something to fill in gaps. They're busy PoC-ing ThousandEyes to get some visibility on a different front. On the network side, we monitor the network components to clear that and make sure that it runs, or assist if there are notable response-time issues, to try and resolve where the issue would be located.

From our company, which is from the vendor side, we have about five or six users. In our client's organization we're expanding every now and then, but currently there are about 50 users, maybe more.

Because of COVID, everything is standing still currently. We started building grids and consolidated views to see what we can display on the centralized screens to improve visibility for Office 365, and those types of things. We would like to get that extra NOC-type of visibility, or an overview of the environment for certain sections. The client's strategy was that the more people that have access to the system, the more people will call us to inform us that there's something wrong in the system or in the environment, before that system even alerts us. The user base plays a big role in how the organization runs.

We are primarily using this solution to isolate network issues and audio issues.

It provides us the information that we need to make decisions. I troubleshoot audio problems every day, and it helps in figuring out what to look at. I can tell almost immediately if it's an RF issue or a network issue. I couldn't do this without Iris Session Analyzer. 

The feature that I have found the most useful is the decode of packets. It gives us a variety of information that helps us in figuring out what to look at. The networks are getting really complex, and without the information that we get from Iris Session Analyzer, we couldn't do our job.

Its graphical user interface is also very easy to use and intuitive.

They can increase flexibility in the search engine. Basically, I go with the information I have at the time. If I could just type in the parameter that I want to search for and its value, it might be easier than having to do the groundwork upfront before I can get my traces. 

We have been using Iris Session Analyzer for almost two years.

Stability could be a little better. It seems like there's a lot of maintenance on it. 

When they're doing maintenance and a part of the network, servers, or NETSCOUT is not going to be available, I get an email. It seems like there's a lot of maintenance because I see a lot of emails. It just seems like it's under a significant amount of dynamic change.

There could be a lot of different reasons for maintenance. It could be because of us moving things around or because of growth. It could also be regional. It's not like none of the NETSCOUT areas work, just the area they are working on in the region isn't available. I won't say it is a point of trouble for us.

There's no issue with scalability, at least none that I'm aware of. I would say, at minimum, a thousand users are currently using it. They are primarily in service delivery, making sure the network is up and running. 

I haven't contacted their technical support. It is a fairly intuitive tool. I'm sure our Operational System Support team has contacted them. 

We used a tool called Empirix or Hammer. I don't think their solution for LTE was very good. They probably weren't in a position to keep up with us, and that's why the company made a decision to go with NETSCOUT.

I liked the layout of how the information was displayed in Empirix. However, there's so much more information in NETSCOUT, particularly in the QCI voice quality.

It was straightforward. I found it intuitive. I never received any real training on it, and yet I didn't have too much difficulty in getting what I wanted out of it.

We have an Operational System Support team that handles the deployment.

I don't know what the cost to buy the solution was, but I doubt if it's a significant part of the budget as far as the maintenance and support are concerned.

I have met some of the NETSCOUT folks, and they were very courteous and helpful. We have a good relationship with NETSCOUT, and it's reflected in the communication and the service that we see from them.

I would recommend Iris Session Analyzer. I couldn't do my job without it. Each company would have to make their own decision because I have no clue about the cost. If not this tool, then go for some other tool that does the same thing.

You just need to be persistent. You can't know everything. When I find something that seems weird, I start digging into it. 

I would give Iris Session Analyzer a nine out of ten. I'm sure there are areas that could be improved, but specifically, I'm unaware of anything major that needs to be done.

We are a telco company and we are using nGeniusONE to do a survey of our core network. We created different services based on nodes and based on services like VoLTE and the like. Our use cases are mainly to provide KPIs and to detect anomalies in case of an issue in the network.

Before we were pretty weak in network KPIs. That's the area where we have improved as a result of the solution, based on the service.

The solution transforms packet wire data into real-time data that is actionable. It helps us with faster detection of issues and allows us to create alerts.

It also provides the right people in our company with the right information in a single pane of glass view. There is always a place for improvement, but it does so. We have created a special dashboard for different teams so that each team has a relevant dashboard for the system.

In addition, nGeniusONE provides us with increased visibility while conducting an IT deployment. When we are launching a new node or a new application, it gives us a way to check that traffic has moved from one node to the other and that we still have the same level of traffic and the same success ratios.

It also helps us to get to root cause quickly, for sure, with the drill-down. If we see an issue on a KPI or we have an alert, we drill down to get into the special cases — tracing and that kind of thing — to detect the root cause.

Using nGeniusONE for unified communication application performance for VoIP helps us with uptime and user experience. We can see, for a given call, if it is a one-way or there are gaps.

The main feature, for us, is the dashboard. That is the main way we are using the solution to detect issues and to create alarms.

The drill-down is definitely interesting.

We are also using another tool from NETSCOUT, for tracing, called Iris Session Analyzer.

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.

I have been using NETSCOUT nGeniusONE for about five years.

The stability could be a bit better. We are working right now to find solutions to improve the stability and we are in discussions with NETSCOUT about that.

The solution's distributed architecture, in terms of being both lightweight and scalable, is pretty good. The ability to distribute the solution is good. We have more and more use cases with virtualized systems, so we need a way to be able to distribute the solution on different clouds and sites.

There are about 100 users.

Previously we were using Tektronix, and that became NETSCOUT. We took nGeniusONE to improve our ability to detect issues. We were mainly working with a tracing system and nGeniusONE brought us more network visibility, with KPIs based on the network itself, and on the traffic in the network.

The initial setup was pretty complex. For me it was complex to configure everything as needed to be efficient: to get all the data, to have some reliability, and some confidence in the data quality. It was time-consuming. We need to understand what was possible, what was the best solution for evaluating a service, etc.

In one sense, the deployment is a never ending story, because each year we have new services and we need more capacity. We are always implementing new things. But the initial deployment itself took us almost a year.

In terms of our experience with NETSCOUT's customer support during deployment and post deployment, here are two levels. The first level was their people who are in direct contact with us and that level was good. When they needed support from development and R&D, at that level we had some quite long delays, at times, and the response was less good.

As for the learning curve, when people are used to working with the system, it's okay. At the beginning we had some training, but now, if a new colleague comes in, we can train him internally. We help colleagues on different teams by giving them training. With one day of training, you can already provide a lot of hints and information. After that, people need to learn by doing.

When it comes to administration, there are three of us who are mainly involved, but it's not 100 percent of the time for any of us. It might be the equivalent of one FTE. I'm a network engineer and I'm mainly involved in the monitoring and probing of new applications. When new services come out I work on increasing the capacity and evolving the system. So I'm not the main user working each day with it.

We have worked directly with a NETSCOUT consultant. We have a reseller, but direct contact with NETSCOUT is very important for me.

We needed this type of a solution. Without it we are fully blind. We can't even launch a service without one solution or another. We needed to put something in place, but I don't have figures or a monetary value for ROI. It gives us visibility.

The pricing is fair.

We have a yearly agreement that covers extensions, etc. There are no additional costs.

We didn't evaluate other solutions much because we already had a probe installed with Tektronix. NETSCOUT was quite a natural way to extend what already existed. We decided not to remove everything that was in place, but to extend instead.

It's a good tool. You need to have a clear view of what you need before you evaluate the system.

Automatic discovery and mapping of client-server relationships is not something we are using much, because we are more at the level of the network and a bit less at the level of all the servers and the internet application server.

The biggest lesson I have learned from using nGeniusONE is that to get good results from the system, you need good knowledge of the network. The system will, for sure, help to find issues, but it's not possible to have someone working with it, someone who doesn't know the network, and have that person fully use this type of system.

We are a solution provider and this is one of the products that we implement for our clients.

It is used for managing traffic that is coming in and our of virtual environments like VMware. We can data mine all of the traffic from the cloud as if it were an on-premises server.

vSTREAM gives us better visibility and reporting about our network infrastructure, allowing for cost-optimization. It shows us where we are losing money with respect to infrastructure.

The most valuable feature is the ASI, which gives us visibility at the nanosecond level.

The interface is user-friendly.

I would like to see improvements made to the user guide. From my personal experience, it is helpful to see a list of steps describing what to do next in different situations. An example is what to do and what to back up in the case of certain types of failure. There are also cases where a customer can't understand specific features. Enhancements to the user guide would be helpful for this.

More features for network fragmentation would be helpful.

I have been working with NETSCOUT vSTREAM for the past year.

This is a stable product.

I would say that this is not a scalable solution.

Our client has between 1,000 and 2,000 employees on their network.

The technical support is very good and they are responsive, although they need to add more phone lines to India or the Pacific region. Really, they need more engineers in support because when you call, it takes between 45 minutes and an hour to connect with an engineer. 

The initial setup is very easy.

vSTREAM is connected to our virtual environment using the MAC addresses of the hardware.

I would rate this solution an eight out of ten.

The generation of KPI-like information that feeds to the nGeniusONE (management) server is the most valuable feature. The vSTREAM itself isn't the only tool you would need, you also need management software. 

None.

The stability is good.

It is scalable. 

Their technical support is very good. 

The initial setup is straightforward. 

vSTREAM is used to get information out of a virtual environment. A lot of the time with these types of products, the monitoring layer implementation lags behind in projects. Customers should take monitoring into account in the project planning and budgeting from the start not just at the end of the project. 

I would rate it an eight out of ten. There is always room for improvement. 

We do pre-analysis using the OptiView of the networks. We also do what is called packet analysis, quick reaction. We go through the site using OptiView, doing data analysis, bring it back and use that. 

We also do the pen screens on migrated sites through Joint Regional Security Stack (JRSS), so when we do the pen screen installs, the ball feeds back to the regional cyber center and into the nGeniusOne. Then, we look at the nGeniusONE to do KPIs, data analysis, and see where the problems are with the network and give reports on it. We try to be proactive regarding the networks using this tool.

Proactive analysis is what we do. Quick reaction is my team's title. We use the tools for proactive analysis of network sites to see where the problems are and what layer the problems at.

It gives us feature view analysis of the network and pre-deployment. It provides the local site better insight by showing them what is going on with their network.

Once we get it online, we have greater visibility on the network and can see where the problems are at.

There are common tools that a lot of our sites use, and when we see the data coming in, we try to pick one (Citrix or SCCM). We can see where they are having problems using the tool, then start building a list of what the dependencies are, and if there is any commonality between this site and that site in the network problems.

We had a site trying to get from point A to point B. They were going through multilayer jumps on the network. We found out it that they didn't have their proxy servers balanced, so everything was going through one proxy server. We used OptiView to find that out.

• Visibility
• Analysis
• Solving future problems that we see, as things come up using nGeniusONE.
• Ease of use
• The performance metrics that it provides. They gives us a proactive analysis of the different applications which are being used on the network. This gives us a better view into where the problems lie.

The nGeniusONE solution is very stable. I don't think we have had any problems with it. It gives us a good view into the networks, helping out the sites that we deal with.

Only problems that we have had are fiber issues going into the TAPs or vSTREAMs, which are usually local site issues. 

It can be scaled with the Multi-Mode TAP solution. We have it big and little sites, e.g., we have a site with 14,000 users and another site with about 3000.

The initial setup is pretty straightforward. We have a build guide that we went through and started in our lab. We modified it, so it's pretty easy to do once you get going.

I worked with NETSCOUT on the deployment.

It has cut our troubleshooting down by days. Once we have a product in place, we show people examples of how it can streamline their troubleshooting process. Getting sites and the government to understand this, that is the biggest obstacle.

Go with NETSCOUT. Versus other tools out there, this is the best tool.

We are getting ready to get the solution for unified communication application performance.

The primary use case is to have the ability to detect issues that a customer would eventually see. It's a more proactive approach for making the customers have a better satisfaction in terms of their usage and performance.

It gives us quicker reaction times and more proactive diagnostics, especially in terms of needing to set up an alarm if a threshold was exceeded.

It gives us a deep package inspection. It provides that sort of visibility. It also has the ability to get the data in real-time.

This solution helps us get to root cause quickly, especially as we dive deep capturing packets.  

• The quick ability to troubleshoot.
• The ability to look forward.
• The ability to develop proactive solutions.

It is the ability to collect data and analyze it, especially key performance indicators. This is before a customer would call to the service center to complain that they have had bad coverage or a dropped call.

While it is good, the single pane of glass view is too high level. It is better for management or someone doing sanity checks. A lot of times, I need to go deeper into the additional screens to get what I want out of it.

We would like to have increased performance in the future. Eventually, we will need more horsepower.

We would like NETSCOUT to add additional topics to the data that it collects, because big data is important going forward.

It's very stable. 

When we first got the tool, there were some performance issues. Eventually, they worked out the issues through various upgrades and server hardware enhancements. That was a plus.

We do have two onsite NETSCOUT engineers, who are excellent. Especially when we encounter an issue, we tell them right away, "We have an issue. Can you fix it?"

We don't have to wait a few days for something to be solved.

The initial setup was a probably a little complex. We had to get things up and running, do field trials, fine tune the performance, then evaluate it under load, and fine tune it again.

We worked closely with NETSCOUT for the deployment. 

We have our own IT department who channels the server, infrastructure, and networking. I'm on the engineering side, and we work directly side-by-side with NETSCOUT. 

We don't use a third party vendor.

Proactive versus a customer having a bad experience: That is the key point. Because you get a bad experience, and you lose customers. You always want tools to make your customer happy.

The solution gives us a forward looking vision. We develop custom applications on top of the data that we collect. It gives us that ability, which is an advantage.

It's definitely decreased troubleshooting time. We get a direct window into the infrastructure and various probes, especially the ability to capture certain KPIs that we look at. Normally, if we didn't have this tool, we would have to collect them under various vendor boxes. That takes time and experience.

Deep packet inspection is the key point for NETSCOUT versus the other competitive tools that we also use.

Take a look at it. If not, you're losing the opportunity to improve your performance in terms of its customer aspects.