ThousandEyes Reviews

My main use case for ThousandEyes is to monitor third-party applications; we monitor BGP paths to the cloud, so if applications are not hosted in our own private cloud, we monitor what's going on in terms of third-party applications.

A specific example of a third-party application I monitor with ThousandEyes is a clinical system called Rio; we monitor them to know the performance because they are not hosted in our own private cloud.

Although we do monitor our own applications hosted by ourselves to see what could be going on from multiple sites into our data center if something is going wrong, my main use case for ThousandEyes remains focused on third-party applications.

The best features ThousandEyes offers include monitoring page load times, assessing how long it takes for an application to load, checking for packet loss and jitter, and monitoring the routing path from the user to the server hosted in the cloud or on-premises. Additionally, you could know if the page is currently loading or not; there are still many more features, but those are what we use at the moment.

ThousandEyes has positively impacted our organization by enabling us to know if a third-party hosted application isn't functioning properly, allowing us to determine what's actually going on and whether the issue lies on our side or with the application provider.

An area where ThousandEyes can be improved is in providing more in-depth packet analysis; we've found instances where ThousandEyes indicates everything is okay, but it's actually not. I would recommend incorporating something similar to Wireshark into ThousandEyes for deeper packet analysis as there are still aspects that ThousandEyes isn't able to determine. When something goes wrong, despite all the investments, certain results remain elusive, so they need to explore areas where Wireshark excels.

The knowledge base around ThousandEyes is quite limited; many engineers are unaware of its existence or the benefits it can provide, and this needs to be addressed. On a rating of 1 to 10, I would give ThousandEyes a maximum of five, indicating that there are many areas for improvement, especially in helping engineers understand how to resolve issues related to third-party hosted applications, as opposed to more recognized brands such as Cisco which have extensive resources for independent study.

Lastly, the servers sometimes require rebooting to monitor applications accurately, which may indicate a potential bug or issue.

I have been using ThousandEyes for almost two years.

ThousandEyes is not very stable; sometimes you have to reboot the servers to get actual results.

Scalability with ThousandEyes is straightforward as you don't really need to scale; it's designed to monitor multiple applications, accommodating 50 or 100 applications simultaneously, and if you need multiple testing points, you just deploy agents at different parts of your network or different sites that you're managing, which it does well.

I have not previously used a different solution, so I don't have any comparisons to provide.

Before choosing ThousandEyes, I did not evaluate other options as I do not make that decision.

There have been multiple instances when the insight from ThousandEyes has helped my team solve a problem faster or avoid downtime. Before we had ThousandEyes, we were not so sure where the problem was coming from, so for example, if a third-party application goes down or becomes very slow, we could never tell whether the problem was coming from the infrastructure side or from the application provider.

The application service provider would often tell us that everything is fine on their end, but after checking our infrastructure, we discovered that every other application was fine except this one, prompting a need for in-depth analysis into what exactly is happening and where the problem is coming from so that it can be properly fixed. We then begin to track what's going on with network path visualization, checking the page load time, jitter, packet loss, and every other component.

My advice for others looking into using ThousandEyes would be to try out a demo to see if that meets their needs and solves their problems.

On a scale of 1-10, this solution rates as a 5.

On-premises

My main use cases for ThousandEyes are troubleshooting slow speeds and investigating disconnection issues that users report.

The historical timeline feature is what I appreciate most about ThousandEyes because when people report that something occurs at a specific time of day, I can set up a test and capture the issue in action.

One of the specific challenges I face with hybrid and distributed enterprise networks that Cisco addresses is SD-WAN visibility, as it can be difficult to see both the underlay and the overlay, creating some visibility gaps.

My impression of the end-to-end visibility offered by Cisco is that aside from those gaps, it captures nearly everything.

Cisco does optimize the experience in a hybrid distributed enterprise setup, and if there is a portion of the network that we cannot see, then that becomes a problem that affects our organization's troubleshooting capabilities.

ThousandEyes could be improved by unifying the GUI with the rest of the Cisco products since it remains legacy from its original state when Cisco acquired it.

I have been using ThousandEyes for approximately five years.

ThousandEyes scales adequately for our needs as my organization grows.

I would rate customer service and technical support as excellent based on my experience. I would give it a rating of 10 because whenever we have any issues, we can typically reach someone who has the knowledge to help us.

Prior to adopting ThousandEyes, I was using traceroutes and packet captures to address similar needs.

My experience with deploying ThousandEyes involved learning how to set up the tests. When I am setting up tests, I have a certain amount of credits allocated for each test, and it is difficult to see how many tests I can set up at one time before exhausting the credits, making it a trial-and-error process.

I have seen a return on investment with ThousandEyes.

My experience with pricing, setup costs, and licensing indicates that licensing is somewhat complicated because of the credits system.

I did not have any specific alternative solutions in mind when considering options before ThousandEyes.

I would rate ThousandEyes an eight on a scale of one to ten, with ten being the best.

Public Cloud

Other

My main use case for ThousandEyes is to monitor network performance like network input/output rates and network latencies, and it is primarily for network monitoring.

For example, I monitor network latencies, network packet usage, identify network connectivity related issues, and check the availability of network devices such as routers and switches using ThousandEyes.

The best features ThousandEyes offers include network performance monitoring, along with APM and server performance infrastructure monitoring, with network performance monitoring being its main area.

Out of those features, the network performance monitor that allows me to see real-time network usage performance across the stack stands out as the most valuable to me, and it is a very advanced feature that ThousandEyes has.

ThousandEyes has positively impacted my organization in terms of network monitoring, network performance monitoring, identifying network graphs and latencies, and monitoring network product availability, which has been very beneficial to our company and projects.

Specific outcomes show that ThousandEyes improved MTTR by 70% and achieved the SLIs and SLAs set by our customers, leading to very positive feedback regarding MTTR, downtime, and high availability of network devices.

ThousandEyes can be improved by offering more comprehensive solutions across the full stack, enhancing their capabilities in application performance monitoring and infrastructure monitoring compared to other tools such as Dynatrace and Splunk Observability Cloud.

I wish to emphasize that they can focus more on APM-related monitoring improvements.

Regarding ThousandEyes's AI capabilities, I notice more hallucination, and they could fine-tune that part, particularly improving the accuracy of analytics for network latency server details.

ThousandEyes is stable. Its scalability is very good.

I have been using ThousandEyes for more than two years now, and initially, at the start of my career, I also used it for around 1.5 years.

ThousandEyes is stable.

Its scalability is very good.

Customer support is very prompt, offering on-demand services and support with separate teams for high-level guidance and break-fix issues, and we are satisfied with the support provided.

Previously, we used Splunk Observability Cloud, but the team observed it lacked network performance monitoring, leading us to choose ThousandEyes for its capabilities in this area.

We did not deploy ThousandEyes ourselves; Cisco manages the platform and provided the SaaS license, so it runs on the client side, and we are not aware of its specific location.

I know we can manage with minimal employees, and there are no significant costs involved for resources or the tool, to my knowledge.

Before choosing ThousandEyes, we evaluated many tools such as Dynatrace and DataDog, but I heard from my management that those are very costly, which is why we opted for ThousandEyes since we were already using the Cisco product, Splunk Observability Cloud.

My advice for others considering ThousandEyes is that if their goal is to monitor network performance, they should definitely consider ThousandEyes.

On a scale of one to 10, I would rate ThousandEyes a six. I chose a six out of 10 because it lacks monitoring features for application performance and database monitoring, especially end-user experience; it excels mainly in network performance monitoring and network device monitoring.

In a hybrid and distributed enterprise network, the specific challenges we face include a lack of performance identification related to network performance, especially in APM trace, when connecting APIs from public cloud to legacy systems.

I assess Cisco's operational efficiency in my IT environment as very useful in day-to-day operations, utilizing proactive monitoring and third-party tool integration to reduce MTTR, such as with ServiceNow.

Cisco optimizes the experience in a hybrid or distributed setup by utilizing agents for distributed tracing, which collect data and send it to ThousandEyes for tracking.

I have observed a lack of end-to-end visibility in Cisco tools, as Cisco offers multiple tools for various observability needs, but there is not a single tool for end-to-end tracing.

The troubleshooting capabilities are strong, but they come from an individual tool perspective rather than a unified platform perspective.

Before concluding, I want to summarize that ThousandEyes excels in network performance monitoring but lacks functionalities in application performance monitoring and digital experience monitoring. I strongly suggest that the ThousandEyes team should focus on improving these areas to enhance the tool's capabilities. My overall rating for ThousandEyes is six out of ten.

Public Cloud

Other

My main use case for ThousandEyes is path monitoring.

I use ThousandEyes for path monitoring to see how my traffic is flowing in my network, what the hops are in between, and then see at what hop exactly the issue occurs whenever it happens. So for example, the recent use cases that we have implemented is the hub-spoke topology for one of our customers wherein they had a hub and multiple spokes. Then we created the paths using ThousandEyes to monitor continuous performance between hub and spokes.

Other use cases would be to monitor cloud performance, checking HTTP URL availability, or web session monitoring, and others.

I think the best features that ThousandEyes offers are path monitoring, and obviously, the HTTP monitoring and the others are also good.

For the path monitoring feature, what stands out to me is the ability to see the unmanaged network. ThousandEyes has a lot of vantage points across the world, it helps us quickly identify whenever there is an issue with an ISP or MSP or even at the cloud site, and how that is visually described is what I find really useful.

ThousandEyes has positively impacted my organization because of the ability to identify issues proactively. Digital experience monitoring is an integral part of observability and monitoring nowadays. I need to know not only what's happening in my network, but also what's happening in the network that's not managed by me.

I have seen specific outcomes and improvements since using ThousandEyes such as reduced downtimes, faster troubleshooting, and identifying root causes faster.

I think ThousandEyes can be improved, specifically the licensing model.

It's too complex, too expensive, and it takes a lot of time to manage the licensing model.

My experience with pricing, setup cost, and licensing indicates that the licensing model is quite challenging. Every path, the frequency of gathering the data, consumes the units, so that's where I think a lot of improvement is needed or a lot of simplicity needs to be added.

I have been using ThousandEyes for probably four years.

ThousandEyes is stable.

ThousandEyes is very scalable.

The customer support is very good.

On a scale of one to ten, I would rate the customer support as an eight.

We haven't used other solutions before.

The setup is easy.

I did not purchase ThousandEyes through the AWS Marketplace.

I think the return on investment is mainly in time saved because the amount of effort needed to troubleshoot an issue when it is with an ISP is saved.

It's too complex, too expensive, and it takes a lot of time to manage the licensing model.

We haven't evaluated any other options before choosing ThousandEyes.

I would not add anything else about the features.

I haven't used the AI capabilities, so I'm not too sure about its accuracy and reliability of output.

We haven't faced any specific challenges with hybrid and distributed enterprise networks that Cisco addresses. ThousandEyes is a great product. The only thing is they need to improve the licensing model.

From ThousandEyes perspective, Cisco indeed optimizes the experience in a hybrid or distributed enterprise setup.

I am really impressed with the end-to-end visibility offered by Cisco through ThousandEyes.

End-to-end visibility from ThousandEyes affects my organization's troubleshooting capabilities because sometimes the problem is not in my network. Sometimes the problem is in the cloud or sometimes the problem is with the ISPs that provide the services, so ThousandEyes is able to quickly identify those and reduces our time to troubleshoot.

I would advise others looking into using ThousandEyes to look at the licensing model and also look at the dashboarding capabilities as well. When I used it last time, dashboarding was not really great, so these two cautions I would give them.

Overall it is a great product, but a few improvements are needed. I would rate this review an eight out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for ThousandEyes is network and endpoint observability.

A specific example of how I use ThousandEyes for network and endpoint observability is running synthetic tests from endpoints against SaaS applications, as well as against egress routers.

The best features ThousandEyes offers include low noise, no false alerts, very early awareness, and reduced MTTR from issues that pop up, as well as an overall awareness and metrics, KPIs out of the environment for client and network performance.

The low noise and early awareness features allow us to become aware and generate alerts to the network operation center when an issue is brewing and also identify whether it is client-side, network-side, or backend.

ThousandEyes has positively impacted my organization by increasing employee satisfaction and reducing outages, saving dollars from idle employees that may have otherwise been having system or network issues, so we have that awareness to troubleshoot right away.

Downtime would be in the tens of hours saved just from being able to pinpoint where an issue is occurring, and a unique feature of ThousandEyes is the path visibility, which shows if an issue is within our corporate network or with a service provider.

One area where ThousandEyes can be improved is possibly having more stats on the endpoint; they may be there, and we may have just not dug deep enough yet to configure it where we can be alerted for endpoint issues itself, and ThousandEyes can do that but requires a little digging.

ThousandEyes definitely has differentiators versus the peers in the space, as there are other tools that are a bit more user-friendly to configure, especially around enterprise agents; for example, when upgrades are required, it sometimes needs a complete de-installation and re-installation of a newer version, which leads to a bit of administrative overhead from time to time, but overall, it has been an excellent product.

I have been using ThousandEyes for three years.

ThousandEyes is stable.

ThousandEyes's scalability seems infinite.

The customer support is excellent.

Positive

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing is that it comes in cheaper than alternatives, and for setup, the package auto-updates, which is certainly a reduced administrative burden.

ThousandEyes is deployed in my organization in a hybrid cloud environment.

The cloud provider we mostly use is Amazon.

I did not purchase ThousandEyes through the AWS Marketplace.

I have seen a return on investment, and while I cannot quantify money, I can definitely say I have saved time.

My experience with pricing, setup cost, and licensing is that it comes in cheaper than alternatives, and for setup, the package auto-updates, which is certainly a reduced administrative burden.

I did not evaluate other options before choosing ThousandEyes.

I advise others looking into using ThousandEyes that the enterprise agent might be their most valuable module, as the endpoint agent certainly gives visibility into the client and can also be used for Webex RoomOS; their other modules are very useful as well, with internet insights being much more robust than DownDetector, which can provide early awareness when there is a global outage with a SaaS provider, for example, so cycles are not spent troubleshooting issues locally that do not reside locally.

ThousandEyes is an excellent product that really provides accurate metrics into network performance as well as the user experience, and I would highly recommend it. I give ThousandEyes a rating of nine out of ten.

hybrid cloud environment

Amazon Web Services (AWS)

I have been using ThousandEyes with this company for two years. The main use case is that we would like to get insights into our calls.

Currently, we are still in the POC state with ThousandEyes, but as of now, we get insights into our calls data and telephony data, which is quite useful for us.

The features I like the most about ThousandEyes are the visualizations that let you see how the call flow went and how many hops it took and everything.

Cisco does optimize the experience in a hybrid and distributed enterprise setup. Our customer has almost four thousand sites, and they use Cisco phones. We also deploy the infrastructure behind it for us to understand how the phones are doing, if the phones are not, and we do proactive testing rather than reactive. That is why ThousandEyes helps us.

We face challenges with hybrid and distributed enterprise networks since we use Cisco, but we also have other third party integrations. When it comes to ThousandEyes, it does not show anything when it is out of Cisco. That is where we have a lack.

My impression of the end-to-end visibility offered by Cisco is that they could do slightly better things.

I think the pricing, setup cost, and licensing for ThousandEyes are too costly. This is a big one. From my perspective, I think the licensing model can be improved because not everybody is a large-scale company.

I have been in the industry for six years.

I would assess the stability and reliability of ThousandEyes as good, with no downtime or crashes or performance issues experienced.

ThousandEyes scales pretty well with the growing needs of our organization.

I would evaluate customer service and tech support for ThousandEyes as good.

Prior to adopting ThousandEyes, we tried to do a POC on Forward Networks.

My experience with deploying ThousandEyes was easy because the tag team was quick and easy to respond.

When we were deciding on ThousandEyes, we were considering other solutions. The competition type would have been Forward Networks.

I would rate this product a 9 out of 10.

My main use case for ThousandEyes is that it checks our product website, and if it flags that it is unable to log in, it checks for all the components from all the agents, which are from different locations. It keeps on scanning every five minutes or every minute, and it flags issues immediately through email alerts.

When we receive email alerts, we thoroughly troubleshoot what is causing the issue, whether it's a false alert or a true alert. If it's a false alert, we receive a recovery email, and if it's a true alert, we don't get recovery alerts. Then we engage the next level of support and keep checking the troubleshooting issue.

There are many situations where ThousandEyes has helped us catch an issue, such as a product login where there was a certification issue. In one of my use cases, the certificates were updated as part of one of the recent changes.

With the help of our monitoring team, we have defined a lot of use cases in ThousandEyes, and we have predefined sets that are very useful for us. That acts as a radar for us.

ThousandEyes positively impacts our organization by flagging issues immediately, which helps us reduce downtime whenever we seize or acknowledge the alerts. That is the benefit of ThousandEyes.

ThousandEyes has helped in a lot of situations, especially before the start of client login hours, by flagging issues immediately so we can resolve them and ensure the product is available all the time.

In my opinion, the best features ThousandEyes offers include its ability to act as a radar, logging in from different regions across the globe and confirming whether our product is working as expected. This is very useful for us.

The global monitoring from ThousandEyes alerts us immediately about issues, and troubleshooting is handled by us, allowing us to resolve the issue before the client reports it.

The alerting and reporting features are all done at the real-time level.

I believe ThousandEyes is working perfectly, but I feel that with more AI integration, it could flag issues with more detailed error information, which would help support engineers immediately pinpoint what exactly is causing the issue.

Regarding needed improvements, I think the user interface could be better. It is sometimes a little confusing and should be very user-friendly, including a guide for how alerts are configured to assist first-time users.

I have been using ThousandEyes for more than five years.

ThousandEyes is stable.

I believe it is scalable.

I deal with customer support through our dedicated team working with ThousandEyes team, and I believe they are doing great.

Regarding ThousandEyes's AI capabilities, I believe they are very capable, and from a security perspective, we haven't found any issues.

I haven't explored ThousandEyes's accuracy and reliability feature much, so if there is a feature that has not yet been introduced to us, I need to explore more on that.

My advice to others looking into using ThousandEyes is to go for it, as they are the best in the market.

I would rate ThousandEyes a nine because there are features I would like to see improved. Not every product can be perfect, and I believe it should evolve to have a more user-friendly UI.

We use ThousandEyes primarily for monitoring our production and BCP servers. We specifically utilize it to monitor URL alerts. We have multiple applications, and at times, URLs may go down due to patching schedules or upgrades. When that happens, ThousandEyes sends an alert, allowing us to see the exact error and client details. This helps us determine what the client is experiencing, and we can then contact the relevant team, such as L2 support, to resolve the issue.

I find the most valuable feature of ThousandEyes is the ability to directly see the client's exact issue. Unlike other platforms where we only receive update notes, ThousandEyes provides the exact error from the client, making troubleshooting more efficient.

ThousandEyes could improve by implementing a similar incident management system like BigPanda or ServiceNow. Having a dedicated incident alert system for URL alerts would help manage noise and streamline operations, especially during patch upgrades.

I have been using ThousandEyes for two and a half years.

I have not observed any instability, like lagging or crashing, with ThousandEyes so far.

I have contacted the technical support at ThousandEyes. There was an instance when the ThousandEyes URL, along with all other URLs, went down due to a network issue. We contacted the support team, and they resolved it within a couple of hours. Their response time and solution were satisfactory.

Positive

I did not use any alternatives before ThousandEyes.

The initial installation of ThousandEyes was easy for us. It was straightforward to understand and allowed us to check and resolve errors efficiently.

Overall, I would rate ThousandEyes nine out of ten. Despite its efficiency, it could still benefit from improved incident management.

We use ThousandEyes for monitoring and troubleshooting, especially when end-users complain about latency or poor performance. We rely on ThousandEyes to provide metrics to see if the problem is related to the local Wi-Fi or the Internet. The main goal for ThousandEyes at our company is monitoring. We also have some integration with our other monitoring systems, and we use ThousandEyes to dive deeper into specific problems when they occur.

From an engineering perspective, we achieve an excellent return on investment by fixing problems rapidly and avoiding business downtime. ThousandEyes helps reduce troubleshooting time by at least fifty percent, allowing our team to quickly support end-users and maintain business operations.

The most valuable features of ThousandEyes are the full monitoring capabilities and the ability to identify the exact location of problems in the path between the application and the end-user. For example, ThousandEyes can notify us about specific paths on the internet that are facing issues, providing detailed insights to our service providers and allowing us to raise tickets and resolve problems. The detailed information ThousandEyes provides about performance issues is crucial for us, enabling us to navigate through various network segments effectively.

When I first started using ThousandEyes, I found it challenging to extract useful information due to the numerous options available. I needed some training to effectively troubleshoot. More detailed documentation explaining the metrics and the testing mechanisms would be helpful. The information is there, but understanding exactly what ThousandEyes is testing to make its conclusions can be obscure.

We have been using ThousandEyes for about six months.

Not too much. Since we deployed ThousandEyes, it has been running pretty well.

ThousandEyes is highly scalable. The only potential issue with scaling up is related to licensing costs, as deploying more agents around the globe could become expensive. However, the product itself is good at scaling because adding more agents enhances our monitoring capabilities.

I have not interacted frequently with their support team, but based on limited experience, I would rate their customer service as very nice. I'd give it an eight out of ten.

Positive

Before using ThousandEyes, we used SolarWinds and also relied on Cisco DNA Center for monitoring. SolarWinds did not help much with comprehensive troubleshooting, and it required ad hoc testing.

I was not part of the deployment team. From what I know, the initial setup wasn’t overly complex, and our engineers received help from Cisco to deploy the product.

Our deployment involved just one or two network engineers along with some help from Cisco, likely around one or two people on the Cisco side as well.

We achieve a very good return on investment by fixing problems quickly, thus preventing users and the business from losing time and money due to poor performance or downtime. For an engineer, the tool speeds up problem identification significantly and improves overall network performance.

The licensing cost could be a potential problem depending on the agreement, especially for smaller businesses. In our company, this was manageable due to existing agreements with Cisco. ThousandEyes licenses are based on the number of flows processed, not just the number of agents deployed.

We did not evaluate any other tools before choosing ThousandEyes.

I would highly recommend ThousandEyes because it can reduce the time spent identifying issues by at least half and provide extensive visibility into network quality.

I'd rate the solution nine out of ten.

ThousandEyes is an AI-based element. 

I felt it is slightly more intuitive, providing more end-to-end service delivery because it’s integrated with AI.

The usage is okay. The tool is helpful. It shows the impact assessment and structures that impact.

For application and user monitoring, we have been using it for different healthcare users. We have different sales-based solutions for healthcare.

Their user monitoring is slightly more practical. We’re really using it in user monitoring and Internet insights, which include customer journeys and creating those elements. That is more practical, I felt.

A few teams are still not using it completely. A few teams are partially adopting it. Only in the US and a few parts of Europe are they use it. But in Japan and a few other Asian countries, they are not using it. Only a few units in the US and Europe are using it.

So, it might add more value as it go into network operations. In the context of healthcare organizations, it might need slight improvement. Otherwise, it is good.

I was in a pure consulting role. See, I work with McKinsey and a few other organizations. What I do is support in bridging. I’m supporting three or four healthcare institutions and also an automobile organization where I see immense potential. 

So, my role is more strategic: how the tool system would help, how it will contribute, and how it will help the product managers and product owners define the roadmap execution. Also, the service management team, how do you look into execution design? My role is more strategic. 

My role is more consulting, insight consulting, and customer data consulting.

In my case, I’m more focused on consulting on this tool system, how it will create interfaces and support other systems to work. For example, patient management systems and how the data would be visualized. I normally work on that element more strategically but not on the execution element. 

For example, Path Visualization is more of an execution responsibility. I normally support the strategic responsibility more from a core area to route mapping, route visualization, highlighting, and grouping.

From a network engineering context, it’s very helpful.

One feature I liked is end-user monitoring. I support a healthcare institution for user-specific VPN gateway and Wi-Fi monitoring. That is slightly more practical. 

Also, I felt the application because we work on hardware systems in hospitals. The network application is really supported. 

But I’ve not explored more because it’s just been two to three months. I still have to look into how AI will be able to support this. I still have to understand the integration challenges we have been facing. So, there are a few elements that need broader experimentation. But in my role, I think that is something I’m able to see in the dashboard system.

It’s evolving; I feel it needs more holistic integration. It needs more improvement. It’s very good, but the integration can be slightly complicated on different platforms.

I used it for a healthcare organization, and the integration was slightly challenging.

In future releases, I would like to explore AI capabilities. AI would be more valuable because it works across different cloud and server systems. It looks into issue detection and insight modeling, so that is something I feel will be very helpful in the near future.

More AI because of compliance and other challenges, not because of the product challenge. It’s about regulations, and we have HIPAA laws in the US and many different kinds of laws. Because of that, these specific elements and certain units don’t allow the tooling system to be fully utilized. We also support a certain segment of healthcare, which is the army healthcare segment, which is more government-controlled. There are certain restrictions in moving into the cloud. That’s where I thought those elements might need some more improvement.

Also, looking into how we’ll be able to use more data visualization. It has it, but it doesn’t give you everything. If you look into the elements of use and so many other elements are there, but the UI/UX also has to be improved a bit, I feel. From a developer’s standpoint, it’s very easy, but from a consultant’s standpoint, there can be more enhancement, like one-click view and one-click report generation. Those things should be more seamless.

I have been using it for three to four months; I’ve been using it for one of the clients.

I would rate the stability a nine out of ten. 

Its scalability is good. 

I would rate the scalability a nine out of ten. Scalability is good.

I have three clients. Because I started this specific project with this client recently. In three to four months, I’ve seen around three organizations that have already started using it. 

I’ve not proposed it to other clients as of now because I have to know the product end to end. Right now, I’m also in more initial exploration from a strategic way. I’ve not seen broad results as of now because it will take some time, right, from the output context.

So maybe after that, I will be able to share it with a few of my other clients. I think it will be very helpful in healthcare if certain things are improved because so many data elements are used for IT security and cloud security. I think that is where the impact would be much higher. 

I also work with a few cloud security organizations. I normally support only enterprise organizations. A few medium-sized businesses, which are more than 10,000 people. Most of my customer base is 20,00 to 200,00 users. I also support organizations with more than 500,000 users. These are a few clients that I’ve been working with for the last 10 to 12 years as a consultant. So that is something I feel would be valuable.

Scalability can be improved because of the UI/UX. If it improves, then it would be much easier from a user context. That is something I felt. Apart from that, I think it’s okay.

Technical teams are good, as far as I know. There are a few bits and pieces, integration challenges happen, initiative, but if the clients have not come up with big conflicts for me at this level, then it’s good news. As the external consultant, if they don’t come back and say, this is burning, then it’s good news. No news is good news sometimes.

They are able to sort it out. They are able to define it, and your customer service team and everyone are collaborating right. So that is okay. I think I’ll rate it high, very high.

Things are not coming to me, and that's a good indicator. So if any conflicts happen, they are not coming. We are able to resolve it either through documentation and ThousandEyes has developer resources and integration documentation. So they’re able to solve it. Also, customer teams might already be supporting them. So that is okay.

Positive

I would rate the pricing an eight out of ten, with one being cheap and ten being expensive. Based on different region specifics. 

This platform has a very big value in the future, but different organizations have different contexts of economic value. And then there are a few challenges. 

From a product context, I don’t know competitive products. Personally, I have not gone into that. So, the pricing can be reasonable based on the PPFC, potential pricing.  

So the price is more suitable for large businesses.  So if I look into 1000 to 1500people organizations, even if they are into NextOps security, of course, there is a huge cost-benefit analysis and so many things I have to validate before I promote or even suggest this tool because it will change the whole infrastructure, execution, and other elements. So I felt that. 

But I felt that this was slightly over there. If you look into the really big value that it pays, it can create. 

Overall, I would rate it around eight out of ten, considering all these elements, because there is scope for improvement. It’s a very good product, but it has more potential for improvement as I go through it.