Logstash output

Hello, I am new to the ELK stack. I have installed logstash stdout output plugin. Can someone tell me where I can see the output of logstash?
(Because I am parsing the message in logstash but it is not showing in Kibana).

FYI we’ve renamed ELK to the Elastic Stack, otherwise Beats and APM feel left out! :wink:

stdout means to the console or logged to the default log file, depending on how you are running Logstash.

hi @anjali can you share your configuration file. and can you tell me which Elastic Stack version you used ?

Thanks & Regards,
Krunal Patel.

Thanks a lot. But i'm still unable to see the output in the log files present in the log folder. My version is 5.6.3. Any advice?

how are you running logstash? systemd?

no, I am running it on win10.
the logstash input comes from filebeat, and output goes to elastic search (visualized on kibana)

Please post your config.

config is all commented.

Settings file in YAML

Settings can be specified either in hierarchical form, e.g.:



size: 125

delay: 5

Or as flat keys:

pipeline.batch.size: 125

pipeline.batch.delay: 5

------------ Node identity ------------

Use a descriptive name for the node:

node.name: test

If omitted the node name will default to the machine's host name

------------ Data path ------------------

Which directory should be used by logstash and its plugins

for any persistent needs. Defaults to LOGSTASH_HOME/data

path.data: C:\apps\logstash-5.6.3\logs

------------ Pipeline Settings --------------

Set the number of workers that will, in parallel, execute the filters+outputs

stage of the pipeline.

This defaults to the number of the host's CPU cores.

pipeline.workers: 2

How many workers should be used per output plugin instance

pipeline.output.workers: 1

How many events to retrieve from inputs before sending to filters+workers

pipeline.batch.size: 125

How long to wait before dispatching an undersized batch to filters+workers

Value is in milliseconds.

pipeline.batch.delay: 5

Force Logstash to exit during shutdown even if there are still inflight

events in memory. By default, logstash will refuse to quit until all

received events have been pushed to the outputs.

WARNING: enabling this can lead to data loss during shutdown

pipeline.unsafe_shutdown: false

------------ Pipeline Configuration Settings --------------

Where to fetch the pipeline configuration for the main pipeline


Pipeline configuration string for the main pipeline


At startup, test if the configuration is valid and exit (dry run)

config.test_and_exit: false

Periodically check if the configuration has changed and reload the pipeline

This can also be triggered manually through the SIGHUP signal

config.reload.automatic: false

How often to check if the pipeline configuration has changed (in seconds)

config.reload.interval: 3

Show fully compiled configuration as debug log message

NOTE: --log.level must be 'debug'

config.debug: false

When enabled, process escaped characters such as \n and " in strings in the

pipeline configuration files.

config.support_escapes: false

------------ Module Settings ---------------

Define modules here. Modules definitions must be defined as an array.

The simple way to see this is to prepend each name with a -, and keep

all associated variables under the name they are associated with, and

above the next, like this:







Module variable names must be in the format of



------------ Queuing Settings --------------

Internal queuing model, "memory" for legacy in-memory based queuing and

"persisted" for disk-based acked queueing. Defaults is memory

queue.type: memory

If using queue.type: persisted, the directory path where the data files will be stored.

Default is path.data/queue


If using queue.type: persisted, the page data files size. The queue data consists of

append-only data files separated into pages. Default is 250mb

queue.page_capacity: 250mb

If using queue.type: persisted, the maximum number of unread events in the queue.

Default is 0 (unlimited)

queue.max_events: 0

If using queue.type: persisted, the total capacity of the queue in number of bytes.

If you would like more unacked events to be buffered in Logstash, you can increase the

capacity using this setting. Please make sure your disk drive has capacity greater than

the size specified here. If both max_bytes and max_events are specified, Logstash will pick

whichever criteria is reached first

Default is 1024mb or 1gb

queue.max_bytes: 1024mb

If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint

Default is 1024, 0 for unlimited

queue.checkpoint.acks: 1024

If using queue.type: persisted, the maximum number of written events before forcing a checkpoint

Default is 1024, 0 for unlimited

queue.checkpoint.writes: 1024

If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page

Default is 1000, 0 for no periodic checkpoint.

queue.checkpoint.interval: 1000

------------ Dead-Letter Queue Settings --------------

Flag to turn on dead-letter queue.

dead_letter_queue.enable: false

If using dead_letter_queue.enable: true, the maximum size of each dead letter queue. Entries

will be dropped if they would increase the size of the dead letter queue beyond this setting.

Default is 1024mb

dead_letter_queue.max_bytes: 1024mb

If using dead_letter_queue.enable: true, the directory path where the data files will be stored.

Default is path.data/dead_letter_queue


------------ Metrics Settings --------------

Bind address for the metrics REST endpoint

http.host: ""

Bind port for the metrics REST endpoint, this option also accept a range

(9600-9700) and logstash will pick up the first available ports.

http.port: 9600-9700

------------ Debugging Settings --------------

Options for log.level:

* fatal

* error

* warn

* info (default)

* debug

* trace

log.level: info


------------ Other Settings --------------

Where to find custom plugins

path.plugins: []

I mean the config doing the processing :slight_smile:

Also please use the code button - </> - to format things, otherwise it's very difficult to read.

input {
beats {
port => "5044"

filter {

    grok {
         match => ["message", "\[%{DATA:timestamp}]%{GREEDYDATA:message}"]
        # overwrite => [ "message" ]
        add_field => {
    time => "%{timestamp}"
    error => "%{message}"

                match => ["timestamp","HH:mm:ss:SSS", "dd/MM/YY HH:mm:ss:SSS", "M/d/YY HH:mm:ss:SSS", "MM/d/YY HH:mm:ss:SSS", "M/dd/YY HH:mm:ss:SSS", "MM/dd/YY H:mm:ss:SSS", "M/d/YY H:mm:ss:SSS", "MM/d/YY H:mm:ss:SSS",
    "M/dd/YY H:mm:ss:SSS"]


output {
elasticsearch {
hosts => [ "localhost:9200" ]
stdout{ codec => rubydebug}Preformatted text

Ahhhh! I didn't know about this code button. Thanks!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.