Update troubleshooting.asciidoc

Fixes #11545
This commit is contained in:
Karen Metts 2020-02-12 18:28:02 -05:00 committed by Karen Metts
parent 0a88578ef1
commit 8c11a95f9f

View file

@ -155,8 +155,8 @@ For basic pipelines, this configuration could be enough to make the problem show
input {stdin{}} output {stdout{}} input {stdin{}} output {stdout{}}
----- -----
To better identify the offending pipeline, {ls} could separate its logs by pipeline. {ls} can separate logs by pipeline. This feature can help you identify the offending pipeline.
Switch on the log per pipeline feature by enabling it, put `pipeline.separate_logs: true` in your `logstash.yml`. Set `pipeline.separate_logs: true` in your `logstash.yml` to enable the log per pipeline feature.
For more complex pipelines, the problem could be caused by a series of plugins in 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. a specific order. Troubleshooting these pipelines usually requires trial and error.