Troubleshooting

Nexvu Retail Sentry is an excellent tool for troubleshooting. In its typical deployment first it is used as a troubleshooting tool as it helps in finding real cause of chronic and random problems that keep evading network engineers and application teams sometimes for months. Nexvu's Retail Sentry puts an end to a common finger pointing and zooms in to the exact source of the problem often in minutes if there is a Nexvu Retail Sentry deployed in the network.

Nexvu's Retail Sentry's visibility into the network traffic makes troubleshooting easy and provides a hero like rewarding experience to its users. Its genius is in its visibility that first pinpoints the problem area, sorts it out to be further drilled down into Network and Application category. This is done by looking at troubleshooting metrics such as Network Delay, Throughput Delay, and Server Delay help narrow the source of the problem to the offending infrastructure components. For Transactional applications there are transaction metrics that help characterize the efficiency of the applications network intercommunications capability. The number of transactions and size of the transactions are important factors when characterizing the network efficiency of an application. . For example, the application that employs a high transaction count and low byte per transaction value will utilize resources significantly less efficiently and have relatively longer response times than that which uses fewer transactions.

Nexvu Retail Sentry allows further drill down into the "Root Cause Analysis" via its simple to use packet capture module. In normal operation The Nexvu Retail Sentry analyzes all network conversations at superficial level only (packet headers) and thus it can stretch its ability to networks with Gigabits of data flowing through and does not miss any information. This also makes it very secure because payload of these packets is not observed or saved. However, when optional packet capture module is added and enabled, one can analyze save and export every part of the conversation - only if an application level troubleshooting is needed.