Options to discard retries caused by 429 errors

[r0b3rt24]

Is your feature request related to a problem? Please describe.
When logstash encounters 429 errors when delivering messages, It will retry infinitely. That ends up in message stuck in memory queue infinitely. If such cases accumulates, it will eventually stall the ingestion.

Describe the solution you'd like
An option to discard all delivery failed after a certain number of retries.

Describe alternatives you've considered
N/A

N/A

[divanshurox]

Hello, we are also encountering a same issue where logstash reports retrying for events with status code 429 and then stops pushing data. Is there some way to push events with status code "429" to DLQ or drop them to get the pipeline going?