mirror of
https://github.com/elastic/logstash.git
synced 2025-04-25 07:07:54 -04:00
parent
0a88578ef1
commit
8c11a95f9f
1 changed files with 2 additions and 2 deletions
4
docs/static/troubleshooting.asciidoc
vendored
4
docs/static/troubleshooting.asciidoc
vendored
|
@ -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.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue