Pipeline ID in Logstash Error Log - multiple pipelines

[lakshmiral]

Having multiple pipelines configured in Logstash through Xpack, it is really hard to identify which pipeline is causing the error as Logstash does not display the Pipeline ID in the Logstash error log. As a result, debugging is becoming a challenge. If something goes wrong, then we need to remove each of the pipeline and verify where the issue is exactly or execute individually for each pipeline which beats the purpose of having multiple pipelines in Logstash.

It will be helpful if logstash can publish the Pipeline ID in the error log.

Elasticsearch version (bin/elasticsearch --version): Elastic 6.2.4 version

Plugins installed: [] Xpack-6.2.4

JVM version (java -version): 1.8.0

OS version (uname -a if on a Unix-like system): RHEL Linux 7

Description of the problem including expected versus actual behavior:
Expected behavior is to print pipeline ID or pipeline details in Logstash error log vs. Actual behavior : If any of pipeline has an issue, logstash just errors out and we need to trace back each pipeline in order to identify which pipeline is errored out or not working.

Steps to reproduce:

Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.

1. Goto Logstash.log file, check for errors - it just dumps all the pipelines errors and does not relate an error with a pipeline ID.

[colings86]

@lakshmiral this issue seems to relate to Logstash rather than Elasticsearch. Therefore I am going to move this issue to the Logstash repository

[andsel]

Closed by PR #11075