Cisco ThousandEyes empowers organizations to assure every digital experience across every network, everywhere, every time.
N/A
SolarWinds Pingdom
Score 9.5 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
We have found ThousandEyes to be more full-featured than many of its competitors. Many of them were more tailored strictly for operating inside a corporate network and weren't flexible enough to adapt to our service provider use case. Other competitors, simply didn't have the …
SolarWinds Pingdom
Verified User
Executive
Chose SolarWinds Pingdom
Pingdom was cheaper with better reporting and API integration.
Unified communications real-time analysis is one of the biggest points of the solution. You can see your traffic path and find issues before, during and after the calls. This is very useful for analyzing VoIP and video conferencing problems like in WebEx, Microsoft Teams and Zoom. It helps to see network issues like packet loss, jitter, or latency that can make call quality bad. Another good use case is checking cloud apps and SaaS services. Many companies use external platforms like Microsoft Azure, 365, Salesforce, or AWS. It lets Networking teams see the network path from users to these services so they can find if problems come from the company network, the internet provider, or the cloud service. Also, it is good for companies using mix of on-prem and cloud. It shows how traffic moves between different parts of the network, so IT teams can see where a problem happens and fix it faster. There are different types of agents that we can use in Cisco ThousandEyes. Enterprise agents can be use for a relative big amount of synthetic test. Endpoint agents are install in user PC or MAC laptops to check network quality from the client side. WebEx devices also have built-in agents that help to see performance problems in meetings, making it easy to find what is causing a bad call. Maybe it's not the best solution if what you want to measure is not HTTPs based or hasn't an API. Also if your scenario is Zoom Rooms, you won't have the same level of integration that it has for WebEx and Microsoft solutions.
I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients
Cisco ThousandEyes does the holistic discovery of the end components, the network components, and it's really fast at identifying where the issue is, which is not normally identified by the classic monitoring tools. So it's quite a fast identifying the issue of the networks and Cisco ThousandEyes also provides a very good real user end user monitoring experience for the end customers. So those are the two real life and also very good examples for Cisco ThousandEyes.
The elephant in the room is going to be cost. ThousandEyes is a great tool, but you will pay for it. There are other services that do a good job at providing a smaller subset of features compared to ThousandEyes. If all you need is that particular subset of features, ThousandEyes may not make fiscal sense for your organization.
As a subset of the cost issue, within the last 18 months or so the pricing on enterprise (local) agents has been modified in a way that seems not to benefit the customer. Previously enterprise agents had a flat monthly cost associated with them with unlimited test usage (the only limit on test usage was based on concurrent tests running at any given point in time). This meant that instead of using a cloud agent and paying per-test, you had the option of spinning up an cheap Digital Ocean droplet and creating your own cloud agent for external testing without using Cloud Agents. When the change was made they eliminated the flat per-agent cost and instead treated the pricing the same as that of the cloud agents but cutting the number of "cloud units" per test in half for tests run from enterprise agents. For organizations with under-utilized enterprise agents, this may be helpful financially, but for organizations that push their local agents to the limit, the cost skyrocketed.
BGP monitor peering sessions have been less than reliable. The data doesn't seem to be an issue, but the sessions seem to bounce or fail altogether on a fairly consistent basis. The routers or servers with which your routers peer sit behind some firewalls that have caused issues in the past.
The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.
The software does it's job extremely well and the system makes it very user friendly to get into. When looking for software I prefer to not need a PHD to operate it. Having a great UI and simple setup makes it easy to include more members of our team to get more value out of the platform.
Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.
There is definitely a learning curve to ThousandEyes, but once you understand how the client deployment works and how to set up monitoring, things go pretty smoothly. I think the initial setting up of clients on endpoints can be a little tricky though.
Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.
You have online support from the tool itself 24/7 and they are very responsive. We also have a specific account manager and specific engineer assigned to help us with very specific questions for our environment. The level of response to our requirements is always super high. We have requested specific features to be added and these have been developed and introduced very quick tot he product (within weeks). Their DevOps and agile approach seems to pay off.
Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.
Our Cisco reps actually had someone teach us a few things about the functionality of ThousandEyes, and it helped a lot. The training was good and we had follow-up assistance as well when we had questions about the monitoring and reporting functions. Overall, we were satisfied with the training and support.
Our implementation was pretty straightforward, with some issues loading clients on endpoints. We didn't have any notable issues, and I don't really have any additional insights.
No one is better than the other. I can get different data and sometimes similar data, it's important to compare values and verify the data between the tools. Additionally, there are other functionalities that ThousandEyes has that the others don't, but it is also the other way around. I will always recommend to have available not 1 or 2, all possible available for your job.
PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem
I think this product would be infinitely scalable since it's all cloud hosted and can support thousands of endpoints if needed. We are only using it for a limited number of endpoints, so we never really considered scalability.
Building the trust from our Merchants is core when you come to renewal time. Trust builds partnerships, builds stickiness and allows for easier upsells or contract renewals.
Having a champion in IT that touts your service is important to the business, it removes a large portion of friction in the business to get services implemented and working to its peak.
Flexibility in pricing can be better. How they measure the number of agents being used can get thorny. When you build and tear down virtual servers a lot it can appear there are more agents running than there are. Once we understood how they measure we were able to better utilize the product efficiently.
Honestly, we have 4 other products that overlap this functionality whose organizations provide far superior support. At this point it is an unnecessary expense.
In my opinion, their lack of support responsiveness and commitment has impacted our IT agility.
