What do you dislike about Elastic Observability?
While Elastic Observability is incredibly powerful, the learning curve can be steep, particularly when it comes to mastering its query language for complex log analysis. As a generalist infrastructure engineer managing diverse environments across Kubernetes (EKS), Docker Swarm, and AWS, I find the initial manual setup and dashboard customization to be quite time-consuming. It lacks enough out-of-the-box, pre-built dashboards that could immediately simplify insights for cloud-native deployments. Additionally, at scale, resource consumption—specifically system memory and disk I/O—can become demanding, and managing index lifecycles requires constant attention to avoid unexpected storage costs and performance bottlenecks. Incorporating more automated configuration assistants and expanding the repository of plug-and-play templates for containerized microservices would significantly reduce the initial onboarding friction and ongoing maintenance toil. Review collected by and hosted on G2.com.
Recommendations to others considering Elastic Observability:
To enhance the user experience and streamline operations, Elastic Observability could benefit from the following improvements:
1. **Enhanced Query Language Documentation**: Providing more comprehensive guides and examples for mastering the query language would help users overcome the steep learning curve.
2. **Pre-built Dashboards**: Offering a wider range of out-of-the-box dashboards tailored for specific cloud-native environments could simplify initial setup and provide immediate insights.
3. **Automated Configuration Assistants**: Introducing more automated tools to assist with initial setup and ongoing maintenance could reduce the time and effort required from users.
4. **Resource Optimization Features**: Implementing features that help manage resource consumption, such as memory and disk I/O, would be beneficial, especially at scale.
5. **Index Lifecycle Management Tools**: Providing more intuitive tools for managing index lifecycles could help prevent unexpected storage costs and performance issues. Review collected by and hosted on G2.com.
What problems is Elastic Observability solving and how is that benefiting you?
Managing disparate environments across AWS, Kubernetes clusters, and containerized workloads previously created fragmented monitoring silos, making end-to-end root cause analysis slow and cumbersome. Elastic Observability solves this by centralizing distributed logs, metrics, and APM traces into a single, unified pipeline.
Having full-stack visibility in one place has drastically cut down our mean time to detection (MTTD) and resolution (MTTR) during production incidents. Correlating deployment changes directly with latency spikes and microservice bottlenecks across our CI/CD pipelines has eliminated guesswork, saving valuable engineering hours each week and ensuring higher system reliability and uptime. Review collected by and hosted on G2.com.