{"id":2362,"date":"2019-11-16T09:01:42","date_gmt":"2019-11-16T09:01:42","guid":{"rendered":"https:\/\/www.gologica.com\/elearning\/?p=2362"},"modified":"2025-04-06T09:01:33","modified_gmt":"2025-04-06T09:01:33","slug":"elk-stack-tutorial-getting-started-with-elk-stack","status":"publish","type":"post","link":"https:\/\/www.gologica.com\/elearning\/elk-stack-tutorial-getting-started-with-elk-stack\/","title":{"rendered":"ELK Stack Tutorial – Getting Started With ELK Stack"},"content":{"rendered":"

In the ELK Stack, ELK stands for Elasticsearch, Logstash,
\nand Kibana. In the ELK stack, Logstash defined as it extracts the logging data
\nor other events from different input sources. Logstash processes the events and
\nlater stores it in Elasticsearch. Kibana defined as a web interface, which
\naccesses the logging data form Elasticsearch and visualizes it.<\/p>\n

In this tutorial, you will learn<\/strong> <\/p>\n

Introduction to ELK Stack<\/p>\n

ELK Stack Architecture<\/p>\n

Introduction to Elastic Search<\/p>\n

What is Logstash?<\/p>\n

What is Kibana?<\/p>\n

Case Studies in ELK Stack<\/p>\n

Introduction to ELK Stack<\/strong> <\/p>\n<\/h4>\n

The ELK Stack is a collection of three open-source products
\nthat are Elasticsearch, Logstash, and Kibana. They all are developed,
\nmaintained, and managed by the company Elastic.<\/p>\n

E stands for Elastic Search: used for storing logs<\/p>\n

L stands for LogStash: used for shipping as well as the
\nprocessing and storing logs<\/p>\n

K stands for Kibana: It is a visualization tool (a web
\ninterface) which is hosted through Nginx or Apache<\/p>\n

ELK Stack is designed to allow users to take data from any
\nsource, in any format, and to search, visualize, and analyze that data in
\nreal-time.<\/p>\n

ELK provides centralized logging that is useful when attempting to identify the problems with applications or servers. It allows you to search all your logs in a single place. It also helps to find issues that occur in multiple servers by connecting their logs during a specific time frame.<\/p>\n

\"\"<\/figure>\n

ELK Stack Architecture<\/strong> <\/p>\n

It is the architecture of ELK Stack which shows the proper
\norder of log flow within ELK. Here, the logs generated from various sources are
\ncollected and processed by Logstash, based on the provided filter criteria.
\nLogstash then pipes those logs to Elasticsearch which then analyzes and
\nsearches the data. Finally, using Kibana, the logs are visualized and managed
\nas per the requirements.<\/p>\n