Logstash overview in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the input plugin in a Logstash configuration.

Elasticsearch

input {
  [1] {
    port => 5044
  }
}

Drag options to blanks, or click blank then click option'

Afile

Binput

Cstdin

Dbeats

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'file' instead of 'beats' for network input.

The beats plugin is used here to listen on port 5044 for Beats input.

2fill in blank

medium

Complete the code to filter logs by adding a grok filter in Logstash.

Elasticsearch

filter {
  [1] {
    match => { "message" => "%{COMMONAPACHELOG}" }
  }
}

Drag options to blanks, or click blank then click option'

Agrok

Bmutate

Cjson

Dcsv

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mutate' instead of 'grok' for parsing logs.

The grok filter parses unstructured log data into structured fields.

3fill in blank

hard

Fix the error in the output plugin to send data to Elasticsearch.

Elasticsearch

output {
  elasticsearch {
    hosts => ["[1]"]
    index => "weblogs-%{+YYYY.MM.dd}"
  }
}

Drag options to blanks, or click blank then click option'

A"http://localhost"

B"localhost:9200"

C"localhost"

D"9200"

Attempts:

3 left

💡 Hint

Common Mistakes

Providing only host without port or only port without host.

The hosts option requires the host and port in the format "host:port".

4fill in blank

hard

Fill both blanks to create a Logstash configuration that reads from a file and outputs to stdout.

Elasticsearch

input {
  [1] {
    path => "/var/log/syslog"
    start_position => "beginning"
  }
}
output {
  [2] {
    codec => rubydebug
  }
}

Drag options to blanks, or click blank then click option'

Afile

Belasticsearch

Cstdout

Dtcp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tcp' instead of 'file' for input or 'elasticsearch' instead of 'stdout' for output.

The file input reads log files, and stdout outputs to the console.

5fill in blank

hard

Fill all three blanks to create a Logstash filter that adds a tag if the response code is 404.

Elasticsearch

filter {
  if [response] [1] 404 {
    [2] {
      add_tag => ["[3]"]
    }
  }
}

Drag options to blanks, or click blank then click option'

A==

Bmutate

Cnot_found

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' or wrong filter name.

The condition checks if the response code equals 404, then the mutate filter adds the tag 'not_found'.

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