Splunk Observability Cloud and Amazon EKS operate in the observability and cloud infrastructure sectors, respectively. Splunk Observability Cloud may have an edge with its comprehensive monitoring capabilities and data integration features, while Amazon EKS is preferred for robust infrastructure management and scalability.
Features: Splunk Observability Cloud provides extensive log management and analysis with fast search indexing and data integration across various environments. It offers custom dashboards and robust monitoring capabilities. Amazon EKS supports deploying microservices with strong orchestration and scalability. It integrates seamlessly with AWS services, offering fast computing speed and autoscaling for cloud-native applications.
Room for Improvement: Splunk users often cite high costs and desire better integration with other tools, enhanced automation, and scalability features. Improvements in user training and cost management are also wanted. Amazon EKS users mention the need for better platform stability, improved documentation, enhanced security features, and reduced pricing. Both platforms have room to improve cost management and user experience.
Ease of Deployment and Customer Service: Splunk Observability Cloud is deployable across public, private, hybrid clouds, and on-premises, though customer service reviews are mixed; some find it responsive, others note slow response times. Amazon EKS primarily deploys in public cloud environments and integrates effortlessly with AWS. It generally satisfies users with customer service, albeit there's a request for better debugging support.
Pricing and ROI: Both Splunk Observability Cloud and Amazon EKS have high costs. Splunk is often seen as expensive, but users acknowledge its value for comprehensive monitoring. Return on investment is typically realized through efficiency improvements. Amazon EKS offers competitive pay-as-you-go pricing but tends to be higher compared to alternatives. Users value its scalability, aligning ROI with operational efficiency.
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.
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.
Amazon EKS is very stable, and when properly configured, I rate it ten out of ten.
I would rate its stability a nine out of ten.
We rarely have problems accessing the dashboard or the page.
Simplifying these will enable more people, not just those with strong foundational knowledge, to work effectively with these services.
A UI could help generate config files, simplifying the process for developers who are not architects.
Currently, some third-party plugins, like certain network plugins such as CNI, Calico CNI, or Cilium, are not fully supported.
There is room for improvement in the alerting system, which is complicated and has less documentation available.
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.
It appears to be expensive compared to competitors.
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 scalability is excellent, allowing us to efficiently handle customer experiences and improve operational efficiency.
Now, with the serverless option, you can deploy everything and AWS handles the infrastructure.
For troubleshooting, we can detect problems in seconds, which is particularly helpful for digital teams.
Splunk APM provides a holistic view of the application.
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 combines log search, data integration, and dashboards for seamless monitoring, enhancing infrastructure visibility and security. Its cloud integration and scalability support diverse environments, improving operational efficiency.
Splunk Observability Cloud offers comprehensive monitoring tools with user-friendly interfaces, enabling end-to-end infrastructure visibility. Its real-time alerting and predictive capabilities enhance security monitoring, while centralized dashboards provide cross-platform visibility. Users benefit from fast data integration and extensive insights into application performance. Despite its advantages, improvements could be made in integration with other tools, data reliability, scalability, and cost management. Users face challenges in configuration complexity and require better automation and endpoint protection features. Enhancing AI integration, alerts, and adaptation for high-throughput services could further improve usability.
What are the key features of Splunk Observability Cloud?In industries like finance and healthcare, Splunk Observability Cloud is implemented for application performance monitoring and infrastructure metrics. Its ability to track incidents and analyze machine data benefits network infrastructure, while distributed tracing and log analysis aid in tackling security threats. Organizations often integrate it for compliance and auditing purposes, enhancing visibility into network traffic and optimizing performance.
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.