How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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.
The primary use case is for network monitoring, event management, packet tracing, and forensics.
Detecting network issues which aren't obvious, more than just node alarms.
The primary use case is troubleshooting.
The primary use case is to monitor our network.
The primary use case is network and application performance management.
We use it for our network capacity performance, for the entire ICM backbone core. In addition, our company uses the solution for unified communication application performance. While it's not my team, there is another team responsible for capacity performance for video and they are using the same NETSCOUT toolset for wireless, wire line, and video.
We used to use it for application debugging, in particular SMS and MMS, but lately, we've been turning towards using it for OpenStack and cloud-issue debugging.
We use it mainly for north-south, and soon to be, again, east-west: Troubleshooting, visibility into the VoLTE cloud that we've designed. Initially, it was very small, baby clouds, per se, but now as we redesign and go to scale, so that we have the visibility we need, we need better tools. We have the infrastructure, but we need to take the next step into the virtual lane. We use the solution for proactive monitoring of remote sites. We have 29 data centers where these clouds are built and we're moving out to edge and we will have even more.
We use it for a lot of VoLTE monitoring and network monitoring in general. Most of our services are being monitored via NG1.
Troubleshooting is our primary use case for the solution.
Troubleshooting our LTE network - any situations that come up in our cellular network. We also use the solution for proactive monitoring of remote sites, as we use it to monitor all the towers in our cellular network, as well as our core applications. We're still in the beginning stages, learning how to use it.
The primary use case is network monitoring for telecoms.
Network troubleshooting is our primary use case.
We use this to investigate various network anomalies, application performance issues, and anything that somebody can't seem to solve in our environment.
Over the years, it's been more for packet-capture troubleshooting. But in the last two or three years, we have been using it for application monitoring and expanded our usage because of voice over IP and the communications stuff. It has really expanded a lot, and we've creating dashboards and reports. Originally, it was just a reactive tool. If there was a problem, we'd go capture something and move on. But it has really expanded quite a bit in the last four or five years.
We use it for when an app team or somebody comes to us and tells us that we have a problem with a server, that they're experiencing slowness, or latency, or the like. We like to take two IPs end-to-end. It will give us a server IP and the client IP, and we can plug that into nGeniusOne to hopefully give us some kind of error codes or a breakdown of what's going on from the packet level of the transaction. Hopefully, it gives us an idea of what's wrong.
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.
Visibility into the network is our primary use case. We're just starting to use the solution for unified communication application performance, but we're not there yet.
The primary use case is network management. We have an older product. We are just now installing the newer product. The older product was primarily used for troubleshooting, which is all I can discuss.
We're using the tool to monitor our LTE and 3G core networks, as well as our 5G connection.
We use NETSCOUT nGeniusOne to troubleshoot our network. At US Cellular, we have our voice over IP network and we try to figure out the impact to the customer.
The primary use case is diagnosing real-time communications for all the Voice over IP on our network. We use this solution for unified communication application performance, specifically for performance monitoring, but especially for the troubleshooting.
We're using it for server health, data analytics, and network monitoring on a daily basis. We also use it for proactive monitoring of remote sites. We have around 180 sites, and we monitor their bandwidth and application usage. In terms of SaaS, that's something we're working on too, and hopefully we'll get it to where we want it to be.
Our primary use case for NETSCOUT nGeniusONE is to monitor what is coming in and out, then distinguish where we have problems in our network.
One use case that we purchased it for is deep packet inspection at a 10-gig level. Prior to that, we only had deep packet inspection up to one gig. We are utilizing the tool right now for deep packet inspection, and for everyday dashboard monitoring to show our customers what their current traffic is, how their everyday business needs are consuming their traffic, and what kind of traffic is specifically on their network. Also, the nGeniusONE is providing TAPs for all of our core traffic and is sending it to our security team for them to sort through and look for security risks. That is actually probably the single biggest purpose we're using it for.
Our primary use for nGeniusONE is packet inspection.
Our primary use case is troubleshooting. We use it to go take a look at application flows, to understand, when we have an issue, if there's some sort of latency or if there's a communication problem or if we're getting some abnormal behavior. Our first troubleshooting step, anytime we have an issue, is source and destination IPs and run a capture. It's the first tool that always gets called in when we're trying to troubleshoot an issue.
This is our traffic analyzer replacement. We use it to provide some functionality for our operations to do live captures so they can manage instant management.
The main application that we use is NetFlow: all the NetFlow traffic, monitoring, bandwidth utilization, top-talkers, etc.