Home/ Site Search Software/ Elasticsearch/ Reviews
Updated on: April 21, 2025
98% SW Score The SW Score ranks the products within a particular category on a variety of parameters, to provide a definite ranking system. Read more
The Heart of the Elastic Stack
54.5%
37.8%
7.7%
0%
0%
Fast Search Capabilities, Easy Integration with other Tools, Powerful Data Visualization, Comprehensive Data Analysis
Steep Learning Curve, High Resource Consumption, Occasional Performance Issues, Complex Query Language
Overall, users find the product to be scalable, reliable, and powerful. They appreciate its open-source nature, flexibility, and ease of integration. Many users highlight its effectiveness in handling large datasets and complex queries. However, some users mention occasional performance issues, a steep learning curve, and the need for skilled professionals for optimal utilization. Opinions vary regarding its user interface and documentation, with some finding them intuitive and others suggesting improvements. Despite these mixed views, users generally agree that the product is a valuable tool for building powerful search and analytics applications.
AI-Generated from the text of User Reviews
Interactive charts,Build in aggregators,mapping support,and its easily accessible dashboard makes kibana very useful and easy to manage.
I do not dislike anything, But it will be helpful if graphs are 3D instead of 2D
I highly recommend others to try Kibana with OpenSearch for application monitoring and data visualization purposes.
We use kibana for data gathering from database and dashboard purpose.
1) Flexibility of integration with almost all the tools and components around the globe.
2) Ease of use.
3) Developer friendly API's and Query mechanism.
4) Super quick.
5) Support for Distributed Computing.
6)Very powerful analytics tool called the Kibana which is the 'K' part of the ELK stack.
1) No multi language support for handling request and response. Means, the request and response can be sent andd received in the same language only. No cross language support.
2) Works on near real time. It means there is a lag of atleast 1 sec between the time of data input and the time when the data becomes available for search.
One must definitely consider using Elasticsearch in their enterprise application suite.
Few reasons being:
1) Did not find any other tool which provides so informative visualisation of logs on a user friendly dashboard.
2) JSON based query language which is easy to learn, adopt and use.
3) Can process millions of records with ease.
4) Can be considered if near real time logging is accepted and real time logging is not required.
1) Easy to use, efficient, scalable.
2) Lot of filters provided by Logstash API's which allows integration with almost all the tools and components from different vendors.
3) Powerful and very informative Kibana dashboard. Can be used to index almost all types of data.
4) Supports Distributed Computing. Data is stored across multiple nodes. Hence, making it fault tolerant and resilient.
5) Very powerful tool for visualization of Logs, events that flow across multiple streaming platforms like Kafka, Spark etc.
6) Filtering based on various criteria to narrow down the search results.
7) Search results can be bookmarked, stored in a file, displayed on a console.
I have been impressed by Kibana's flexible layout, which makes it easy to visualize large volumes of data in one place quickly. Kibana has allowed me to put everything I need to see right at my fingertips to make real-time decisions.
It would be great to have more support materials to guide new users in connecting their data and setting up their visualizations. I am intrigued by the machine learning options and would love to understand that more, but I struggle to find suitable materials.
I would undoubtedly recommend Kibana for anyone looking to find patterns in their time-series or production data.
Kibana allows us to keep in the know on the performance of our systems that lead to customer experience. It has enabled our teams to become more productive and allocate our resources where most needed.
There are a bunch of things that I like about Kibana:
1. Beautiful visualization: The visualization provided on the interface is a very handy tool during debugging.
2. It also provides an interface to monitor and manage our Elastic cluster
3. We can filter logs on the basis of various parameters. This has come out to be the most important tool in our daily work and especially during incidents.
There is nothing I dislike. It is going great with the application. The details we are provided are very specific and you can also use Search API and python packages to integrate with your scripts.
We manage our Elastic clusters and also store logs with Kibana. We use Kibana as a source of debugging for various incidents internal to our software as well as external.
Speed! ElasticSearch is FAST. It is also flexible. You can create very complex index structures, with filters, aggregations, vast array of sorting options, structuring your documents in a 'noSQL' way and deploy it either on one node or multiple nodes for performance and spreading the load across multiple devices. It works on a local server as well as in the cloud.
It is hard to get started with the syntax, the DSL, understanding the intricacies. I also don't like that they deprecate things too fast. Before you can learn how everything works and you manage to implement it, a new version comes out and some of the features are deprecated. The syntax is quite hard to get a hold of and knowing where everything goes is a challenge when you are starting out. The documentation on the website is quite hard to navigate, most of the time you find yourself on the wrong version and the examples don't apply. Many times, the examples are out of date and do not work, even if you are on the correct version.
Start simple!
I have developed my own e-commerce search engine, integrated with my e-commerce applications. We've increased speed and relevance of results in our website searches as well as added capability for filtering, sorting, scoring, relevance tweaking and more things we could not do with our previous search engine.
Elasticsearch works on Lucene which makes it perform searches on the index/metadata available. It is also good enough to perform an analysis of the searched content.
It just works with any cloud/ on-prem environment.
Elastic nodes require to have a large amount of memory and storage in order to work.
Our Elastic is hosted on Azure and we have been using premium disks for better IOPS which results in big cost
We have using Elasticsearch hosted on Azure Cloud to perform searches on our storage blobs which has the project data from the last 60 years
We are also ingesting our events generated in Azure to Elasticsearch with the help pipelines in Logstash
Most likely functions are fuzziness, synonyms and other all functions.
There is nothing that I can say that dislike this product.
I am recommending to use Elasticsearch and move your application backend side (I mean the part where frontend call to backend retrieve a data) to Elasticsearch
It's easy to use, I am switching my application backend API call side to ElastSearch.
Elastic search worked on the top of Lucene Engine .Elastic search is an open source search engine which is very good in performance. As Elastic search is a document oriented database that is why it worked on full text search that is why it is fast in searching . I like the performance of elastic search.
Till now everything is good, I personally feel good while using elastic search.
I used elastic search for searching logs while implementing ELK stack to monitoring logs. I feel elastic search good because it is very fast in searching and also scalable.
Elasticsearch support JSON format which makes it a lot easier for developers to integrate it with the backend. It has a powerful REST API and creates redundancy to avoid the loss of data.
When doing many search request, the server shutdowns sometimes. Also, the speed of accessing the data even when using the bulk API is low.
I advice anyone looking for a NO--SQL search engine supporting document types to take a look at elasticsearch. Its not hard to setup and I'm sure you will not regret it.
I worked on elasticseardh during my internship. My Job was to create a NO-SQL clusters and store data comming from an ETL tool in them. I choosed elasticsearch because it support document types and has a very powerfull java API.
Looking for the right SaaS
We can help you choose the best SaaS for your specific requirements. Our in-house experts will assist you with their hand-picked recommendations.
Want more customers?
Our experts will research about your product and list it on SaaSworthy for FREE.
Best way to analize and store million log traces in graphs. The best big data open source platform
The timestamp fields are very restricted. It should be more open and automatically detecting the needed timestamp
Now we can use big data to analyze million traces for our customer devices, with different dashboards such as time series or geographical maps.