TrustRadius Insights for Elastic Observability are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Simplicity and Ease of Use: Users have praised Elastic Observability and Elasticsearch for their simplicity and ease of use. They appreciate how easy it is to set up these tools in their environment with minimal research, trial, and error. The combination of Elasticsearch and Kibana is particularly liked for its user-friendly interface, making data analysis convenient.
Powerful Visualizations: Several reviewers have mentioned the powerful visualizations provided by Elasticsearch and Kibana. Users find the various visualizations, including graphs, charts, and tables, very helpful in analyzing data. They appreciate the ability to create interactive charts and easily visualize large volumes of data in one place quickly.
Efficient Log Searching and Analysis: Many users have highlighted the efficient log searching and analysis capabilities of Elasticsearch. They find Elasticsearch's log filtering and modification feature easy to use and modify. Users also appreciate the option to sort logs in ascending or descending order, which facilitates data analysis. The ability to search for multiple fields in a single query is another feature that has been positively mentioned by reviewers.
Lets us monitor the performance and health of our mission-critical services with the speed of Elasticsearch. I use it for web server log analytics, searching for vulnerabilities and changes to the file logs and system metrics traffic. Elastic Observability has great search functionality and dashboard visualizations and ElastiFlow to monitor the real-time traffic. We save a lot of time. It does the job extremely well.
Pros
Fast and speedy search engine
Indexes large amount of data
Fault tolerance and high availability OOB
Cons
Difficult to setup/maintain
Search pattern bar could be more user-friendly
Premium subscription features are very expensive
Likelihood to Recommend
Great platform for managing application and server logs at a large scale. Elasticsearch can be integrated into 3rd-party software. For example, when combined with Kibana, beats, and logstash to build a full ELK stack it is very powerful and extremely useful for log evaluation, analysis showing detailed information, and creating a monitoring system.
VU
Verified User
Employee in Information Technology (201-500 employees)
Elastic observability is mainly used in main problems like Managing many servers of a production deployment. It becomes very difficult to correlate logs and view performance metrics very easily. And Having no ability to detect and resolve these issues by users before they are reported. these are the problems that can be solved by this elastic observability in our company.
Pros
Open source codebase.
APM integration.
Documentation.
Cons
User Interface.
Dashboarding.
Charting issues.
Likelihood to Recommend
We can use this Elastic Observability in our business problems such as Creating internal/operational efficiencies issues, customer relations/service, and business process outcomes issues. This product has a lot of features for the above problems. But this product may be having some issues when charting purposes. But it can adjust for that purpose.
Managing many servers in a production deployment makes it very difficult to correlate logs and view performance metrics. Tracking issues reported by the end-user is nearly impossible (if at all) in a timely manner. These issues cannot be detected and resolved before users report them.
Pros
Open source code base
Community support
Is fast in processing
Cons
No aspect that interferes negatively.
Likelihood to Recommend
When data is fully correlated, more products are integrated to enrich the overall experience, but data sources need to be standardized to take full advantage of this. Elasticsearch is very efficient. It is more useful for data analysis and anomaly detection than distributed analysis or application debugging. I don't know how to manage mass production deployments without this tool, without the metrics, correlation, and monitoring provided by the elastic stack, we would be blind to system operation and severely limit our ability to respond to questions in a timely manner.
VU
Verified User
Analyst in Information Technology (11-50 employees)
We utilise Elastic in our organisation to keep track of all the logs generated by the various internal services that we have running; we utilise it for monitoring in general but a frequent use case involves looking at logs for incident response purposes to figure out what is actually happening and try to understand any potential impact to the application so that we can take steps to avoid any downtime or negative consquences
Pros
Licensing model is fair compared with other vendors that charge much more
Ability to scale and ingest a lot of data without having to worry too much about performance issues that may crop up
Searches return very fast
GUI searching interface and filters are intuitive and suitable for new users
Cons
The DSL advanced search syntax query language can be confusing to use as you have to maintain correct JSON formatting at all times
More integrations with other common alerting/monitoring/ticketing platforms
GUI hasn't had an update in a while, could benefit from an overhaul with more modern elements
Default dashboards are suitable but there could be room for improvements e.g. more advanced custom dashboards
Likelihood to Recommend
Elastic is a great solution if you want to self-manage your data collection, don't want to pay excessive licensing costs to other vendors for features which are only rarely used and want a competent log aggregation system that returns results very quickly. Scalability is not an afterthought since you can easily grow your log searching and retention resources as the needs of the organisation grow. More and more vendors are building their proprietary solutions on top of Elastic so I believe the open source product will only keep on growing in adoption and getting better each year