Cisco ThousandEyes empowers organizations to assure every digital experience across every network, everywhere, every time.
N/A
Splunk Observability Cloud
Score 8.5 out of 10
N/A
Splunk Observability Cloud aims to enable operational agility and better customer experience through real-time AI-driven streaming analytics allowing accurate alerts in seconds. It is designed to shorten MTTD and MTTR by providing real-time visibility into cloud infrastructure and services.
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.
Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.
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 first one is its Kubernetes container monitoring.
I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.
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.
You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.
We will definitely renew and maybe even extend our usage of ThousandEyes. We have been using ThousandEyes now for a couple of years and it has shown us major benefits. With the new options it offers for SD-WAN for us it is a no brainer to renew our current licenses
Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net
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.
When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.
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.
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.
Kentik Synthetics is a newer competitor of Cisco ThousandEyes. Both do very similar things but Cisco ThousandEyes currently is the more mature platform. However, the pricing of Synthetics is very attractive. It does not have the robustness of Cisco ThousandEyes or the off-net test leveraging (# of outside companies partnered with them) but has made many improvements in the past 2 years.
Splunk Infrastructure Monitoring provides far superior options for anybody using a complex hybrid multi-cloud environment and allows both your SOC and NOC to work together on the same data while driving their own insights. We found other products are still in the old world view of servers and agents residing together within a single data centre, but modern apps are no longer like this.
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.
