NetScout, well known for its high-performance network monitoring systems, has entered the application performance monitoring market with a probe-based system called TruView Live that uses a probe named Pulse. Watch the NFD11 presentations by NetScout. The probes create synthetic transactions for web, VOIP, and video traffic. The physical probes are Linux-based processors that are powered via a PoE connection, making them small and easy to deploy. Of course, you have to have PoE switches for them to work out of the box. Separate voice VLANs are properly handled properly, but only SIP voice is currently supported (no Cisco Skinny protocol).
The Advantages of Probes
I like probe-based systems because they can be easily deployed and provide good visibility into problems that affect applications. Many customers are more successful with application probes than they are with complex network monitoring systems. However, like any network management system, it does require that someone manage the probe locations, monitor the reports, and take corrective action when a problem is reported.
The Pulse is useful in networks where visibility is limited or nonexistent. A VM version is available for installation in public cloud deployments. Monitoring the traffic between the corporate network and the public cloud provides another level of visibility over networks and infrastructure that other tools cannot monitor. Probes are also useful where the application traffic may not be present at all times. Tests can be run during times when the real applications are not running. So VOIP connectivity to remote sites can be checked even when no one is at the site.
TruView also provides about 10 probe sites located around the world from which customers can configure tests to monitor their web infrastructure. Being able to monitor from multiple sites is a very useful feature and should be expanded to additional sites worldwide.
The Disadvantages of Probes
One of the biggest problems with probes is keeping the software updated. NetScout eliminates this disadvantage by creating a process in which the probes perform automatic updates.
Installation and power are another common problem. The Pulse is a very small form factor, avoiding the problem of mounting and power that larger probes present.
Suggestions for NetScout
The NetScout Pulse comes in a small box that includes the hardware and a pair of AA batteries that power the unit when doing an initial installation where PoE isn’t available. The batteries do not last very long, so a PoE connection is required for any real monitoring. There should be an option to order the Pulse with an Ethernet power injector for sites where the switch infrastructure doesn’t provide PoE. Otherwise, the customer must be aware of the need for PoE and must procure power injectors from another source.
The Pulse has a unique code that must be input to the NetScout portal to enable the device. But upon looking at the exterior of the box, there was no corresponding barcode that matched the device’s code. A customer who orders tens or hundreds of Pulse probes will have to use a manual process to enter all the codes. An external bar code and a process for entering probe IDs in bulk are going to be critical for large unit sales.
As mentioned in the disadvantages above, the web server that runs on the Pulse should be secured with at least a self-signed certificate, so that connections to the Pulse are encrypted. In modern security-conscious environments, it is important to take every security step possible.
NetScout should add more protocols, such as mail and ping, the latter of which was conspicuous by its absence. The existing traceroute functionality should be enhanced to show changes in the path over time, which may indicate that a network problem is due to a path change.
None of the above suggestions are show-stopper problems and its advantages outweigh the disadvantages. The current Pulse has some of the symptoms of a new product. It will be interesting to see how quickly NetScout moves forward with improvements.
For a conversation about your own organization’s network and application monitoring needs, feel free to reach out.
Disclaimer: The vendors at NFD11 do not pay delegates for blog posts. They paid indirectly for my travel and lodging to attend NFD11.