Repository navigation
Conversation
|
|
||
| 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. |
There was a problem hiding this comment.
I'm not sure this is quite right, or if we even can change this setting from the command line.
Although we use the Java System Property ls.pipeline.separate_logs in the log4j templates (and one would ordinarily set Java System Properties with -Dproperty=value), it looks like on startup we stomp on the existing value of that property without first reading it, stetting to to be the value held in pipeline.separate_logs from logstash.yml:
java.lang.System.setProperty("ls.pipeline.separate_logs", setting("pipeline.separate_logs").to_s)
There was a problem hiding this comment.
@yaauie you are right, many thanks to point it out. Removed and rephrased a little bit
|
Any further comments or additions? We can expand this question later if needed. |
|
@andsel Any further comments or additions? We can expand this question later if needed. |
|
LGTM |
Pipelines vary wildly, and it's nearly impossible to offer prescriptive steps for troubleshooting. Perhaps we can help by offering some general guidelines, things to try, etc.
This is a basic start. I'm hoping that we can expand with more tips and guidelines now and over time.
PREVIEW: http://logstash_11545.docs-preview.app.elstc.co/guide/en/logstash/master/troubleshooting.html#ts-pipeline