User Tools
Writing /app/www/public/data/meta/development/applications/kibana-elasticsearch-filebeat.meta failed
development:applications:kibana-elasticsearch-filebeat
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:kibana-elasticsearch-filebeat [2017/12/04 16:22] – adsilva | development:applications:kibana-elasticsearch-filebeat [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | === Centralized Logging with Filebeat, ElasticSearch and Kibana === | ||
| + | As of the time of writing this, the logs are stored on the server where the application runs. The process of debugging, searching and garnering insights on the logs is very difficult. | ||
| + | |||
| + | Hence, | ||
| + | |||
| + | **The architecture of this setup is as follows:** | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | As we can see in the diagram, Filebeat is a light weight local daemon that runs on every server where our applications run. | ||
| + | |||
| + | The only job of a Filebeat daemon is to collect logs from multiple log files that are generated within a server and publish them over to Elastic Search. | ||
| + | |||
| + | The path to one or more log files can be configured through a "// | ||
| + | |||
| + | === Role of Elastic Search === | ||
| + | |||
| + | The role of the Elastic search instance is to store and index the logs as per the format sent by Filebeat and to allow for future searching and retrieval. | ||
| + | |||
| + | === Role of Kibana === | ||
| + | |||
| + | Kibana acts as an UI and allows for visualizing, | ||
| + | |||
| + | |||
| + | === Technical Information === | ||
| + | |||
| + | The Filebeat binary is usually deployed to /// | ||
| + | |||
| + | The deployment is done through a Filebeat Ansible Role, for more information, | ||