What is our primary use case?
TruView had a very unique view for displaying network monitoring and response times. It had a matrix called the end-user response time that captured application, network, and server responses in one matrix. It allowed easy identification of issues, whether it was an application, network, server, or backend problem. I haven't seen any software that provides the same level of quick troubleshooting and drill-down capabilities as TruView. Most other systems out there are not as quick or specific in scrolling down to settings or specific details.
What is most valuable?
The most valuable feature for us was the ability to monitor sites and get a nice overview of all the data in a single view. It provided easy visibility of the top servers or sites for application response times and usages.
So data visibility is a strong point of this solution. It provides an easy view to see the top ten for specific servers or sites, especially for application response times and usages.
What needs improvement?
One area that could be improved is the reporting features. In the version transformation from ten to eleven, the platform changed from a Windows-based platform to a Linux-based platform. As a result, the previous reporting feature using Crystal Reports was no longer available. Instead, we had to generate PDF dashboard reports, which were not as flexible. It would be great to have better reporting options in the future.
When it comes to future releases, TruView is reaching its end-of-life, so they are not developing or selling it anymore. However, the replacement software from NetScout, called NetScout Engineers One Monitoring Software, is close but more focused on engineering and technical aspects. It would be great if the new software could provide similar views and data representation as TruView, as there are still a few things that our customers would like to see but are missing in the current solution. For example, improvements in data representation.
For how long have I used the solution?
I have been using TruView for around ten years. Currently, we have it installed for one of our customers who use it.
The customer purchased the hardware, and now it's reaching its end-of-life phase. It's already in the system, so it's nearing its shelf life. We are in the process of replacing it with a new monitoring software from NetScout.
We are currently working with version 11.
What do I think about the stability of the solution?
I would rate the solution's stability an eight out of ten. As long as you consider all the Fluke and NetScout products. It's important not to jump to the latest patch immediately, as that may not improve the reliability. This rating is based on the company's historical performance.
My recommendation would be to follow a reasonable timeline when applying patches. For major releases, such as transitioning from version one to version two, it's advisable to wait a bit before upgrading. However, for incremental releases within the same version, like moving from 1.1 to 1.2 or 1.3, most of the bugs are typically resolved, making the system stable.
What do I think about the scalability of the solution?
I would rate the scalability of the solution around six out of ten. In the past, before the availability of clustering, scaling TruView was not as straightforward. You couldn't simply add resources like disk space or CPU processing power. Instead, you had to upgrade or export the databases and import them onto a new server. However, nowadays, with more advanced software, you can add additional devices and increase processing power and performance.
We have over 100 users using this solution. Our clients are enterprise businesses, specifically in the banking environment.
How are customer service and support?
Over the past three years, I have had an excellent experience with TruView's customer service and support. While there's always room for improvement, they have been consistently helpful and responsive.
How would you rate customer service and support?
How was the initial setup?
I would rate my experience with the initial setup a six out of ten, where one is difficult and ten is easy to set up.
TruView is usually deployed in an enterprise environment on-premises. For a standalone server, the deployment basically takes about two hours. So, if you're really motivated, you can have the system fully deployed in a day, provided you have all the necessary information and the deployment process goes smoothly.
So, the whole process can be completed within a day. Once it's up and running, you can start using it, although configuring data feeds and other customer-specific aspects may take additional time, depending on their change processes.
The initial steps involve gathering information, such as addressing host names and following the customer's change process. You also need to consider the environmental aspects, like space and sufficient cooling. Additionally, if you don't have all the necessary information, you still need to log individual changes to monitor branches and sites, which can take some time. It depends on the customer's change process cycle. So, you need network engineers to configure everything.
We have an automated system for central deployment that allows network engineers to push configurations within a few hours. The speed and automation of certain processes depend on the customer's environment and the tools they have available.
What about the implementation team?
It takes around four to five engineers to load the server during the initial setup process. It's a fully automated deployment process from the CD, where you run it, and it takes care of everything. Along the way, it asks a few questions that you need to answer to complete the network configurations. After that, you need to start working on configuring it, which may take some time.
The system deployment is well-documented, and the engineers from the partner company have provided us with guidance and training. It just takes some time to explore and configure specific sections of the system to make it work effectively.
The system is deployed, and you need some knowledge to configure specific sections of the system. Luckily, our partners showed us training on how to deploy it, and their tech engineers were available to assist if we encountered any issues. There was also online training available. So, everything is there, but you still need to play around the system on your own. They won't provide all the details on a platter because, at the end of the day, they also want to make money through advanced training and sales.
What's my experience with pricing, setup cost, and licensing?
There are certain licensing costs. For example, if you use NetFlow, you need to purchase a license depending on the size of your connector. Similarly, for voice monitoring, you need a separate license. Apart from that, I'm not aware of any additional costs.
What other advice do I have?
Currently, TruView is no longer available for purchase. It's not really suitable for small to medium-sized businesses. It's more cost-effective and designed for enterprise monitoring. So, my advice would be to consider the size and requirements of your organization before deciding.
Overall, I would give TruView an eight. It has evolved over time, and I've never encountered any major issues with it. Customers can easily find what they are looking for within a few clicks, and it enables them to quickly troubleshoot and resolve issues. The system provides an extensive range of views and performance monitoring, allowing for quick problem identification and resolution.
Which deployment model are you using for this solution?
On-premises