mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 14:47:19 -04:00
parent
7549824fcb
commit
d057e8bae0
1 changed files with 4 additions and 0 deletions
4
docs/static/troubleshooting.asciidoc
vendored
4
docs/static/troubleshooting.asciidoc
vendored
|
@ -155,6 +155,10 @@ For basic pipelines, this configuration could be enough to make the problem show
|
|||
input {stdin{}} output {stdout{}}
|
||||
-----
|
||||
|
||||
To better identify the offending pipeline, {ls} could separate its logs by pipeline.
|
||||
To switch on the log per pipeline feature is sufficient to enable `pipeline.separate_logs` in your `logstash.yml`
|
||||
or passing the `-Dls.pipeline.separate_logs=true` on command line.
|
||||
|
||||
For more complex pipelines, the problem could be caused by a series of plugins in
|
||||
a specific order. Troubleshooting these pipelines usually requires trial and error.
|
||||
Start by systematically removing input and output plugins until you're left with
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue