Tracking down bad ingest pipeline senders

So at some point it would appear my pipeline names got changed and so i'm recieving this error a lot with debugging on:

[2017-12-12T01:21:44,884][DEBUG][o.e.a.b.TransportBulkAction] [i-0b38fb9c609ca9464] failed to execute pipeline [go-log-pipeline] for document [go-2017.12.12/doc/null]
java.lang.IllegalArgumentException: pipeline with id [go-log-pipeline] does not exist
at org.elasticsearch.ingest.PipelineExecutionService.getPipeline( ~[elasticsearch-6.0.0.jar:6.0.0]
at org.elasticsearch.ingest.PipelineExecutionService.access$100( ~[elasticsearch-6.0.0.jar:6.0.0]
at org.elasticsearch.ingest.PipelineExecutionService$2.doRun( [elasticsearch-6.0.0.jar:6.0.0]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun( [elasticsearch-6.0.0.jar:6.0.0]
at [elasticsearch-6.0.0.jar:6.0.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_141]
at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_141]
at [?:1.8.0_141]

Trying to track this down I moved the logging up to TRACE but that yielded little results. Is there any way to get this log to include a src address? It would be very helpful for tracking down that run-away filebeat sender in a cluster of 1k nodes.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.