Logstash record_last_run updated on output issue


Why Logstash (JDBC input plugin) is recording the "Record Last Run" timestamp in the metadata file even if there is an issue on the output ?
I had an connection issue (due to network) to the Elasticsearch instance but the last run timestamp is updated for my pipeline.
Is there any way to do avoid this ?


Inputs send events to the pipeline and their responsibility ends there. You could try configuring persistent queues, which try to ensure that data in the pipeline is delivered to the output.

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