Splunk Observability Cloud and Google Kubernetes Engine both operate in the cloud-based technology management category. Google Kubernetes Engine appears to have the upper hand due to its seamless integration with Google's ecosystem and cost-effective pricing model.
Features: Splunk Observability Cloud offers robust log analysis, custom dashboard creation, and data integration, making it valuable for real-time troubleshooting. It effectively supports application performance monitoring and provides easy data visualization. Google Kubernetes Engine manages containers effortlessly, provides managed services, and integrates seamlessly with Google's ecosystem, offering capabilities like autoscaling and easy deployment suitable for cloud environments and microservices.
Room for Improvement: Splunk Observability Cloud could improve in integration with external tools, UI customization, and pricing. Challenges with scale and stability are noted. Google Kubernetes Engine users report a need for better documentation, third-party tool integration, and improved application-level security. Enhancement in configuration and backup features is also suggested.
Ease of Deployment and Customer Service: Splunk Observability Cloud is flexible across on-premises, hybrid, and cloud environments but faces challenges in technical support responsiveness and deployment complexity. Users experience varying support efficiency. Google Kubernetes Engine, primarily deployed in public and hybrid clouds, is praised for ease of deployment, though support reliability and documentation clarity need improvement.
Pricing and ROI: Splunk Observability Cloud's high cost can be a barrier, and competitive products offer similar benefits at lower prices, impacting its pricing appeal. Google Kubernetes Engine has a flexible, competitive pricing model considered cost-effective, offering significant operational efficiency and visibility returns, enhancing positive ROI for many users.
By migrating from AWS to Google Cloud Platform, we have saved a lot of time and money.
Problem resolution typically takes between two and five days, which isn't very helpful.
They did not have a clear answer.
If any issues arise, we can raise a vendor case, and resolutions are provided in a timely and accurate manner.
The autoscaling capabilities of Google Kubernetes Engine have significantly impacted our operations.
We've used the solution across more than 250 people, including engineers.
I would rate its scalability an eight out of ten.
We rarely have problems accessing the dashboard or the page.
I would rate its stability a nine out of ten.
When looking at the web interface, it feels kind of slow due to the many features involved.
It would be helpful if I could easily find log information in a particular namespace without needing to write certain labels.
Log observability could be made easier so someone from high school can use it without having technological expertise.
It would be beneficial if server details could be retrieved directly in synthetic monitoring.
Customers sometimes need to create specific dashboards, particularly for applicative metrics such as Java and process terms.
There is room for improvement in the alerting system, which is complicated and has less documentation available.
Google is considered cheaper compared to AWS, making it suitable for smaller to medium companies concerning cost.
The on-demand nodes are quite expensive.
It appears to be expensive compared to competitors.
Splunk Observability Cloud is expensive.
The most valuable aspect of Google Kubernetes Engine (GKE) is its managed nature, which significantly reduces the burden on our platform team.
GKE is easier to understand and use than Elastic Kubernetes Service.
What I find most valuable is the ability to focus solely on my product without worrying about the Kubernetes infrastructure itself.
It offers unified visibility for logs, metrics, and traces.
For troubleshooting, we can detect problems in seconds, which is particularly helpful for digital teams.
Splunk APM provides a holistic view of the application.
Kubernetes Engine is a managed, production-ready environment for deploying containerized applications. It brings our latest innovations in developer productivity, resource efficiency, automated operations, and open source flexibility to accelerate your time to market.
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.
