Splunk Observability Cloud and Amazon EKS compete in the cloud services sector. Splunk has an edge in monitoring and data visibility, whereas Amazon EKS excels in microservices deployment and scalability.
Features: Splunk Observability Cloud offers robust log analysis, fast search indexing, and customizable dashboards enhanced by OpenTelemetry. Its focus is on precise monitoring and performance optimization. Amazon EKS provides strong orchestration capabilities for microservices deployment, simplifying application management with features like Fargate for infrastructure abstraction.
Room for Improvement: Splunk Observability Cloud could improve integration with third-party tools, documentation, and reduce pricing complexity. There is also a need for enhanced automated feature integration and log interface usability. Amazon EKS needs better pricing transparency, stabilized upgrades, and improved support for non-cloud environments to enhance user experience.
Ease of Deployment and Customer Service: Splunk Observability Cloud is versatile in deployment, handling on-premises and hybrid models, though some users face setup challenges. Amazon EKS operates primarily in the public cloud with a focus on managed Kubernetes. Customer service for both platforms is generally responsive, but Splunk's complex issues can delay resolutions. Amazon EKS leverages AWS's robust support infrastructure.
Pricing and ROI: Splunk Observability Cloud is often seen as expensive, affecting long-term adoption despite its ROI in visibility and productivity. Its pricing is data-centric. Amazon EKS offers flexible, competitive pricing appealing to large enterprises, though costs can increase based on usage patterns. EKS is a cost-effective choice within AWS’s ecosystem, while Splunk’s pricing is justified by its extensive feature set.
We have cost explorer available, and a bill forecast based on usage allows us to determine whether resources are underutilized or overutilized.
It's a fast deployment, with very good documentation, and it's really helpful.
I can recommend using it to save costs and for faster deployment, better performance, security, and easy clustering.
Using Splunk has saved my organization about 30% of our budget compared to using multiple different monitoring products.
Anyone working in front-end management should recognize the market price to see the true value of end-user monitoring.
We have a paid subscription that provides priority support.
Amazon's technical support is quite good, especially for those who purchase support services.
Having to know what questions to ask is essential.
They often require multiple questions, with five or six emails to get a response.
Support from Splunk is not very helpful because Splunk doesn't have a dedicated APM; they only have one APM engineer in Korea.
They did respond to us, but they did not explicitly inform us about the feature's absence.
The ability to scale based on requirements by deploying additional containers is a strong point for Kubernetes.
This allows us to scale our applications or APIs as needed, offering reliability through the automation of scaling processes.
It can scale very well according to needs, and it doesn't have any issues with scalability.
We've used the solution across more than 250 people, including engineers.
I would rate its scalability a nine out of ten.
The issue is mainly about pricing because if they want to monitor more, it costs money.
Amazon EKS is very stable, and when properly configured, I rate it ten out of ten.
Amazon EKS is stable.
I would rate its stability a nine out of ten.
We rarely have problems accessing the dashboard or the page.
Unlike NetScout or regular agents for APM, RUM has many problems during the POC phase because customer environments vary widely.
Simplifying these will enable more people, not just those with strong foundational knowledge, to work effectively with these services.
Amazon EKS can be improved by having the maintenance of Kubernetes versions managed better, as everything is handled by the Kubernetes team and possibly a separate team at AWS.
Adding logging would be a valuable improvement.
There is room for improvement in the alerting system, which is complicated and has less documentation available.
Improvements in dashboard configuration, customization, and artificial intelligence functionalities are desired.
Customers sometimes need to create specific dashboards, particularly for applicative metrics such as Java and process terms.
The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups.
Now, it stands at six or seven due to optimizing our workload.
As Amazon is a pay-per-use service, our usage levels are high, so I would desire if Amazon could provide certain discounts or credits for customers who utilize a lot of resources.
Splunk is a bit expensive since it charges based on the indexing rate of data.
It appears to be expensive compared to competitors.
Splunk is a little expensive, however, it is in line with the current market pricing.
The most beneficial aspect of Amazon EKS is that it helps manage the Kubernetes master node, so I don't need to maintain the master node, including tasks like upgrading.
The main benefits that I received from using Amazon EKS are that it is a managed cluster and offers simplicity.
By default, if you just install Amazon EKS, you can deploy your application, but to have it enterprise-ready, you have to configure a number of other things that will boost productivity.
Splunk provides advanced notifications of roadblocks in the application, which helps us to improve and avoid impacts during high-volume days.
For troubleshooting, we can detect problems in seconds, which is particularly helpful for digital teams.
It offers unified visibility for logs, metrics, and traces.
Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.
EKS is the best place to run Kubernetes for several reasons. First, you can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design. Second, EKS is deeply integrated with services such as Amazon CloudWatch, Auto Scaling Groups, AWS Identity and Access Management (IAM), and Amazon Virtual Private Cloud (VPC), providing you a seamless experience to monitor, scale, and load-balance your applications. Third, EKS integrates with AWS App Mesh and provides a Kubernetes native experience to consume service mesh features and bring rich observability, traffic controls and security features to applications. Additionally, EKS provides a scalable and highly-available control plane that runs across multiple availability zones to eliminate a single point of failure.
EKS runs upstream Kubernetes and is certified Kubernetes conformant so you can leverage all benefits of open source tooling from the community. You can also easily migrate any standard Kubernetes application to EKS without needing to refactor your code.
Splunk Observability Cloud offers sophisticated log searching, data integration, and customizable dashboards. With rapid deployment and ease of use, this cloud service enhances monitoring capabilities across IT infrastructures for comprehensive end-to-end visibility.
Focused on enhancing performance management and security, Splunk Observability Cloud supports environments through its data visualization and analysis tools. Users appreciate its robust application performance monitoring and troubleshooting insights. However, improvements in integrations, interface customization, scalability, and automation are needed. Users find value in its capabilities for infrastructure and network monitoring, as well as log analytics, albeit cost considerations and better documentation are desired. Enhancements in real-time monitoring and network protection are also noted as areas for development.
What are the key features?In industries, Splunk Observability Cloud is implemented for security management by analyzing logs from detection systems, offering real-time alerts and troubleshooting for cloud-native applications. It is leveraged for machine data analysis, improving infrastructure visibility and supporting network and application performance management efforts.
We monitor all Container Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.