Logstash configuration when failing to handle message

Hi!
Recently I started to integrate logstash into our infrastructure, and while reading the documentation I didn’t quite understand how to handle bad messages.

My current flow is as follows: Application -> rabbitmq -> logstash -> elastic.
I want to add a case where if a message fails (bad content, too many tasks on the cluster…) logstash will send back to the RabbitMQ to a queue named BAD.
Is that an option?

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