Problem with Logstash logs

Dear all,

I I would like to get know where is logstash logs. My goal is to have logstash logs in /data01/logstah/logs

Please help

Here are my configs:



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: "logstash"

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 /data01/logstash/data

------------ 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: 1

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

path.config: /etc/logstash/conf.d

Pipeline configuration string for the main pipeline

config.string: /etc/logstash/conf.d

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: true

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

config.reload.interval: 3600

Show fully compiled configuration as debug log message

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

config.debug: false

------------ 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


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

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

Bind address for the metrics REST endpoint ""

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


  • fatal
  • error
  • warn
  • info (default)

* debug

* trace

log.format: plain

path.logs: /data01/logstash/logs

log.level: info,warn,error

#path.logs: /data01/logstash/logs

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

Where to find custom plugins

path.plugins: []


status = error
name = LogstashPropertiesConfig

appender.rolling.type = RollingFile = plain_rolling
appender.rolling.fileName = /data01/logstash/logs/logstash-%d{yyyy-MM-dd}.log
appender.rolling.filePattern = /data01/logstash/logs/logstash-%d{yyyy-MM-dd}.log
appender.rolling.policies.type = Policies
appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
appender.rolling.policies.time.interval = 1
appender.rolling.policies.time.modulate = true
appender.rolling.layout.type = PatternLayout
appender.rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c] %-.10000m%n

appender.json_rolling.type = RollingFile = json_rolling
appender.json_rolling.fileName = /data01/logstash/logs/logstash-%d{yyyy-MM-dd}.log
appender.json_rolling.filePattern = /data01/logstash/logs/logstash-%d{yyyy-MM-dd}.log
appender.json_rolling.policies.type = Policies
appender.json_rolling.policies.time.type = TimeBasedTriggeringPolicy
appender.json_rolling.policies.time.interval = 1
appender.json_rolling.policies.time.modulate = true
appender.json_rolling.layout.type = JSONLayout
appender.json_rolling.layout.compact = true
appender.json_rolling.layout.eventEol = true

rootLogger.level = ${sys:ls.log.level}
rootLogger.appenderRef.rolling.ref = ${sys:ls.log.format}_rolling


input {
redis {
enabled => true
hosts => [""]
type => "redis-input"
# these settings should match the output of the agent
datatype => "pattern_channel"
key => "logs*"
codec => json

  # We use json_event here since the sender is a logstash agent
  format => "json_event"


output {

elasticsearch {
#type => "all"
#embedded => false
enabled = "True"
hosts => [""]
port => "9200"
sniffing => true
manage_template => false
index => "logs-%{+YYYY.MM.dd}"
document_type => "%{[@metadata][type]}"
timeout => "30"
max_retries => "3"
codec => json


Never mind those configuration files. What inputs, outputs, and filters do you have?

Corrected info provided and added input-output config

Use a file output to store logs in the local file system.

How can i do it correctly?

For example

output {
  file {
    path => "/path/to/desired/file"

Thanks a lot, Magnus!

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