There are two main uses for Elasticsearch:
You want Elasticsearch when you do a lot of text search, where traditional RDBMS databases do not work very well (poor configuration, acts like a black box, low performance). Elasticsearch is very customizable, extensible through plugins. You can quickly create a reliable search without much knowledge.
- Recording and analysis
Another question is that many people use Elasticsearch to store logs from different sources (to centralize them), so they can analyze them and make sense out of it. In this case, Kibana becomes comfortable. It allows you to connect to the Elasticsearch cluster and immediately create a visualization. For example, Loggly is created using Elasticsearch and Kibana.
Keep in mind that you do not want to use Elasticsearch as your primary data store. The reasons are here: How reliable is ElasticSearch as the primary data warehouse against factors such as loss of record, data availability
Update
It seemed to me that the second part is no longer annoying, in fact the fact that Elastic, as a company, is doing very well last year. Thanks to the current DevOps movement, CI / CD pipelines, an increase in the number of indicators from different sources, ELK has become the choice of factual for monitoring infrastructure, it is no longer just a distributed text search engine RESTful. It has an amazing set of products:
- Logstash (tons of data entry)
- Beats
- Filebeat
- Metricbeat
- Packetbeat
- Winlogbeat
- Kibana
- X-Pack (premium)
- Alerts
- Reports
- Security
- Machine learning
- Cross data center metrics
A community-built ecosystem grows around the ELK stack, which extends current features, few of which are worth mentioning:
- Elastlerler
- Shield protector
Evaldas Buinauskas Oct 22 '15 at 16:08 2015-10-22 16:08
source share