Logstash overview in Elasticsearch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Logstash?

Logstash is a tool that collects, processes, and sends data to a storage system like Elasticsearch. It helps organize data from many sources into a format that is easy to search and analyze.

beginner

Name the three main parts of a Logstash pipeline.

The three main parts are: Input (where data comes from), Filter (where data is processed or changed), and Output (where data is sent).

beginner

What is the role of filters in Logstash?

Filters change or enrich the data. For example, they can parse text, remove unwanted parts, or add new information to make data easier to analyze.

beginner

How does Logstash help in a real-life scenario?

Imagine you have logs from many computers. Logstash collects all these logs, cleans and organizes them, then sends them to Elasticsearch so you can search and understand what happened easily.

intermediate

What formats can Logstash input support?

Logstash can take data from many formats like files, databases, message queues, or network streams. This makes it flexible to work with different data sources.

What is the first stage in a Logstash pipeline?

A Storage

B Filter

C Input

D Output

The input stage is where Logstash receives data from various sources.

Which Logstash component modifies or enriches data?

A Filter

B Input

C Output

D Index

Filters are used to process and change data before sending it out.

Where does Logstash send data after processing?

A Input

B Output

C Filter

D Parser

The output stage sends processed data to destinations like Elasticsearch.

Which of these is NOT a typical Logstash input source?

A Files

B Message queues

C Databases

D Web browsers

Web browsers are not a direct input source for Logstash.

Why is Logstash useful in managing logs?

A It collects, processes, and organizes logs for easy searching.

B It stores logs permanently.

C It deletes old logs automatically.

D It creates logs from scratch.

Logstash helps by collecting and preparing logs so they can be searched and analyzed.

Explain the three main stages of a Logstash pipeline and their roles.

Think about where data comes from, how it changes, and where it goes.

Describe a simple real-life example where Logstash helps manage data.

Imagine handling many logs from different computers.

Practice

1. What is the primary role of Logstash in the Elastic Stack?

easy

A. To store data in a database

B. To visualize data with dashboards

C. To collect, process, and forward data from various sources

D. To secure the Elastic Stack with authentication

Solution

1. Step 1: Understand Logstash's function

   Logstash is designed to collect and process data from many sources before sending it to storage or analysis tools.

2. Step 2: Compare with other Elastic Stack components

   Elasticsearch stores data, Kibana visualizes it, and security features handle authentication, so these are not Logstash's main roles.

3. Final Answer:

   To collect, process, and forward data from various sources -> Option C

4. Quick Check:

   Logstash = Data collection and processing [OK]

Hint: Remember: Logstash handles data input and processing [OK]

Common Mistakes:

• Confusing Logstash with Elasticsearch or Kibana
• Thinking Logstash stores data permanently
• Assuming Logstash manages security

2. Which section in a Logstash configuration file defines where data comes from?

easy

A. filter

B. input

C. output

D. codec

Solution

1. Step 1: Identify configuration sections

   Logstash config files have three main sections: input, filter, and output.

2. Step 2: Match section to purpose

   The input section specifies data sources, filter modifies data, and output sends data elsewhere.

3. Final Answer:

   input -> Option B

4. Quick Check:

   Data source = input section [OK]

Hint: Input section = data source definition [OK]

Common Mistakes:

• Choosing filter or output instead of input
• Confusing codec with input
• Thinking output defines data source

3. Given this Logstash config snippet:

input { stdin { } } filter { mutate { add_field => { "new_field" => "value" } } } output { stdout { codec => rubydebug } }

What will happen when you type 'hello' and press enter?

medium

A. The input 'hello' is printed with an added field 'new_field' set to 'value'

B. The input 'hello' is discarded and nothing is printed

C. An error occurs because 'add_field' is not valid here

D. The input 'hello' is printed without any changes

Solution

1. Step 1: Analyze input and filter

   The input reads from standard input (stdin). The filter adds a new field named 'new_field' with value 'value' to each event.

2. Step 2: Analyze output

   The output prints the event to stdout using rubydebug codec, which shows all fields including added ones.

3. Final Answer:

   The input 'hello' is printed with an added field 'new_field' set to 'value' -> Option A

4. Quick Check:

   Filter adds field, output shows it [OK]

Hint: Filter adds fields; output shows full event [OK]

Common Mistakes:

• Thinking input is discarded
• Believing add_field causes error
• Assuming output prints raw input only

4. Identify the error in this Logstash config snippet:

input { file { path => "/var/log/syslog" } } filter { grok { match => { "message" => "%{SYSLOGTIMESTAMP:timestamp}" } } } output { elasticsearch { hosts => ["localhost:9200"] } }

medium

A. Elasticsearch output hosts must be a string, not an array

B. Missing closing brace in filter section

C. Grok pattern syntax is incorrect

D. File input path should be an array, not a string

Solution

1. Step 1: Check file input syntax

   The 'path' option for file input expects an array of strings, not a single string.

2. Step 2: Verify other sections

   Filter grok syntax and output hosts as array are correct according to Logstash documentation.

3. Final Answer:

   File input path should be an array, not a string -> Option D

4. Quick Check:

   File path = array required [OK]

Hint: File input path must be an array even for one file [OK]

Common Mistakes:

• Using string instead of array for file path
• Misreading grok pattern syntax
• Thinking output hosts must be string

5. You want to collect logs from multiple servers, add a tag with the server name, and send all logs to Elasticsearch. Which Logstash configuration approach is best?

hard

A. Use multiple input sections with file paths and add tags in filter section, then output to Elasticsearch

B. Use one input section with a wildcard path and add tags in output section

C. Use multiple output sections for each server and add tags in input section

D. Use filter section only to read files and add tags, then output to Elasticsearch

Solution

1. Step 1: Understand data collection from multiple servers

   Multiple input sections allow specifying different file paths per server.

2. Step 2: Add tags in filter section

   The filter section is the right place to add tags like server names to enrich data.

3. Step 3: Output all processed logs to Elasticsearch

   The output section sends all enriched logs to Elasticsearch for indexing.

4. Final Answer:

   Use multiple input sections with file paths and add tags in filter section, then output to Elasticsearch -> Option A

5. Quick Check:

   Input for sources + filter for tags + output to ES [OK]

Hint: Input for sources, filter for tags, output to Elasticsearch [OK]

Common Mistakes:

• Adding tags in output section
• Using filter to read files (wrong place)
• Multiple outputs instead of inputs for servers